3 ms·
> I'd rather break free, not change masters. Unless you have the volunteer army necessary to run the hosting yourself, you're going to be changing to a new mas
by geofft 11y ago
> I'd rather break free, not change masters.
Unless you have the volunteer army necessary to run the hosting yourself, you're going to be changing to a new master anyway. You just need to make sure it's a master you can leave at any moment.
So get a domain name and point it at GitHub Pages, and deal with git for the timebeing. At any point (either if GitHub goes bad, or someone's enthusiastic about setting up something else), you can repoint that domain name to another host, far more easily than you can change octave.sf.net to point somewhere else.
I agree that switching to octave.github.io would not actually help anything other than the immediate problem.
- jordigh 11y agoWell, we do have those volunteers/employees on the GNU servers. We also can pay for our own hosting. We'll probably go one of those routes.
- nadams 11y ago> Unless you have the volunteer army necessary to run the hosting yourself You don't need an army (depending on the solution). But setting up gitlab/rhodecode/indefero/srchub/Gitolite/custom scripts for a single project is kind of overkill. I've used rhodecode and whenever they released an update it would take me hours to update it. I've never been happier to fork indefero and get off of google code.
- sytse 11y agoGitLab CEO here, thanks for mentioning us. We care deeply about making updating fast. Our Omnibus packages should install in 2 minutes and we recently introduced a package server to make updates just as snappy.
- marcinkuzminski 11y agoRhodeCode CTO, thanks for mentioning us. With our new cross-platform installer, it takes just few minutes to update running instances, and it's actually a one-liner to run the upgrade. Thanks for providing feedback !