all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: david larsson <david.larsson@selfhosted.xyz>
To: t@fullmeta.me
Cc: help-guix@gnu.org,
	Help-Guix <help-guix-bounces+someone=selfhosted.xyz@gnu.org>
Subject: Re: Guix as remote dev machine
Date: Sat, 30 Apr 2022 13:07:27 +0200	[thread overview]
Message-ID: <1b1626d32d8d594bb8eec5371b4047e2@selfhosted.xyz> (raw)
In-Reply-To: <0bfaa5f2-558a-4109-a19f-de918eaef637@www.fastmail.com>

On 2022-03-21 15:09, t@fullmeta.me wrote:
> Hi Guix.
> 
> I'm trying to come up with a reasonable way to use my Guix machine
> sitting in the attic as my remote development server. This presents
> several challenges. Locally I would typically follow these steps:
> 1. Create a project dir with guix.scm describing (possibly empty) 
> package
> 2. `guix shell` or start a container, with entire system if I need to
> e.g. run a db
> 3. start emacs from that shell or container forwarding to my main 
> DISPLAY
> 
> When attempting to do something similar remotely, you very quickly run
> into issues. X forwarding to a Linux machine kinda works, but sadly on
> OSX, which I have to use as a client, XQuartz X server implementation
> can't deal with hi DPI and the end result is miserable. Then there're
> potential rendering issues when your remote server doesn't even have a
> graphics card. We're sadly left with ssh + terminal Emacs. However,
> just ssh and then follow the above steps won't be enough. When your
> ssh session goes down, it'll take everything with it.
> 
> I hear you say `tmux`. I thought so too, but fresh `guix package -i
> tmux` gives me `Incorrect locale LC_all, LC_CTYPE or LANG` when I try
> to run it. Weird, seeing how this is attempted on Guix SD. No matter.
> Lets just go with `screen`, which seems to work. Then follow the above
> steps.
> 
> This sort of works and how I would imagine most people attempting this
> would end up with. It leaves me itchy though. I mean, do I even need
> that `screen` there when `emacs --daemon=name` exist? Latter will
> happily detach itself from your tty and persist across ssh sessions.
> Problem of course is the 2nd step above, which assumes we spawn a
> shell (possibly run a container, maybe even the entire system). I
> wonder if there's a way to avoid the intermediate `screen` or `tmux`
> completely. Way I understand it, `guix shell`, `guix shell -c` and
> `guix system --container` are Unix processes. Could they be detached
> or put under some group or smth? I mean, screen works ok, but I
> wonder.
> 
> Thanks

Hello Mr t!

I suggest checking out: guix search xpra

Then the Arch linux wiki has pretty good usage tutorial that could most 
likely work for forwarding of individual application windows. Im 
uncertain how it works for full desktop forwarding on Guix.

Best regards and good luck,
David




  parent reply	other threads:[~2022-04-30 11:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 14:09 Guix as remote dev machine t
2022-03-21 16:08 ` Brian Woodcox
2022-03-22 23:47   ` t
2022-03-22 23:54 ` t
2022-04-30 10:16 ` zimoun
2022-04-30 11:07 ` david larsson [this message]
2022-04-30 14:54   ` david larsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1b1626d32d8d594bb8eec5371b4047e2@selfhosted.xyz \
    --to=david.larsson@selfhosted.xyz \
    --cc=help-guix-bounces+someone=selfhosted.xyz@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=t@fullmeta.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.