Christian Grothoff transcribed 2.6K bytes: > On 12/30/18 3:46 PM, Devan Carpenter [dvn] wrote: > > The current site is also not automatically generated from git, no? Why > > should that be a blocker for switching? > > Simple: the new site is generated differently, so this needs some > sysadmin time. >
I see what you're saying. The output is just static files though, so for now it could be a manual step to generate when there are changes, and move to the correct folder. If it's on the old server (sam) then we could have a user which has a clone of the git repo, the tools to build, and an output folder which served by apache. Whomever has access to this user can update the site. > On 12/30/18 8:47 PM, Devan Carpenter [dvn] wrote: > > I'll also add that we can just run the new website on the legacy server > > until firefly.gnunet.org is ready, if it is really too much trouble to > > get a daemon which can route http requests and serve static html up and > > running. > > On the old server, for various reasons only I shall be root, so I'm the > bottleneck there. And I'm not hopeful. > > On the new server, well, several people have full access, so I'm not the > only bottleneck anymore, so I have more hope ;-). > Yes, that's a bit better. However, I am of the understanding tha the current OS has been hampering progress a bit. I would propose that we have a discussion on this list to determine the software stack which is most suitable for the project's needs. If the case is that that the entire machine is not solely dedicated to supporting the GNUnet project, then we should be using virtualization (kvm, libvirt, etc.) to allow us to have a (or multiple) dedicated environment[s], which wouldn't get in the way of other groups or users of the server. - devan
signature.asc
Description: PGP signature
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
