The HTTP uploads are stored in /var/www/xmpp.kosmos.org now. Added that a couple days ago.
(It's actually possible to write custom upload services, so we could do sth with RS in the long term.)
The HTTP uploads are stored in `/var/www/xmpp.kosmos.org` now. Added that a couple days ago.
(It's actually possible to write custom upload services, so we could do sth with RS in the long term.)
I have added backups as part of #9. Backups are running on Andromeda (no changes have been made to the existing ejabberd setup)
Does that mean you're already running that PR code against the current server? Because if yes, that seems kind of dangerous, and if no, then how do we have backups before/in order so we can run the PR code without potentially losing anything?
> I have added backups as part of #9. Backups are running on Andromeda (no changes have been made to the existing ejabberd setup)
Does that mean you're already running that PR code against the current server? Because if yes, that seems kind of dangerous, and if no, then how do we have backups before/in order so we can run the PR code without potentially losing anything?
Does that mean you’re already running that PR code against the current server? Because if yes, that seems kind of dangerous, and if no, then how do we have backups before/in order so we can run the PR code without potentially losing anything?
I have only executed the backup recipe on andromeda. The kosmos-ejabberd::default recipe has to be added to the run list of andromeda for the rest of the code to be executed. The PR code will have to be executed on an another server first, since it also updates ejabberd to 18.12
> Does that mean you’re already running that PR code against the current server? Because if yes, that seems kind of dangerous, and if no, then how do we have backups before/in order so we can run the PR code without potentially losing anything?
I have only executed the backup recipe on andromeda. The `kosmos-ejabberd::default` recipe has to be added to the run list of andromeda for the rest of the code to be executed. The PR code will have to be executed on an another server first, since it also updates ejabberd to 18.12
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Extracted from https://gitlab.com/kosmos/chef/issues/22
The HTTP uploads are stored in
/var/www/xmpp.kosmos.orgnow. Added that a couple days ago.(It's actually possible to write custom upload services, so we could do sth with RS in the long term.)
I have added backups as part of #9. Backups are running on Andromeda (no changes have been made to the existing ejabberd setup)
Does that mean you're already running that PR code against the current server? Because if yes, that seems kind of dangerous, and if no, then how do we have backups before/in order so we can run the PR code without potentially losing anything?
I have only executed the backup recipe on andromeda. The
kosmos-ejabberd::defaultrecipe has to be added to the run list of andromeda for the rest of the code to be executed. The PR code will have to be executed on an another server first, since it also updates ejabberd to 18.12Ah, got it. Good idea.
I thought backups are already in place for ejabberd? (Said in the last call.)