3 ms·
1. Very frequently. The reason this launch took so long was in large part due to reconfiguring how we merge the differences between .com and the installable (FI
by kneath 15y ago
1. Very frequently. The reason this launch took so long was in large part due to reconfiguring how we merge the differences between .com and the installable (FI/Enterprise). Previously, it was painful and slow and lagged embarrassingly behind. But now it should be no more than a week or a month at most behind .com so long as you upgrade your instance.
2. The instance will lock you out (no web interface, cannot push to repos) but you own all your data so you will never lose your content.
- hillad 15y agoHow are the updates delivered? New OVF?
- kneath 15y agoThe OVF will be updated infrequently — there is a software package you upload in a management interface that installs the new software and configures your instance with the updates. It's pretty seamless — download a file, upload it, wait a few minutes for install and you've got an updated version of GitHub Enterprise.
- lloeki 15y ago> 2. The instance will lock you out (no web interface, cannot push to repos) but you own all your data so you will never lose your content Does that mean one can still clone repos?