Restarting Vidjil - Revision history

Meidanis: English prose.

2023-12-28T11:00:21Z

English prose.

← Older revision		Revision as of 11:00, 28 December 2023
Line 1:		Line 1:
	Sometimes a Vidjil instance needs to be restarted, such as when the application is down or when you need to reload it ~~for some reason~~. Another important aspect of performing a restart is whether or not the Vidjil instance in question is the production server. ~~As such~~, below ~~are presented~~ two sets of instructions on how to perform this task, one for the production server and one for test servers in general.		Sometimes a Vidjil instance needs to be restarted, such as when the application went down for unforeseen reasons or when you need to reload it. Another important aspect of performing a restart is whether or not the Vidjil instance in question is the production server. Therefore, we present below two sets of instructions on how to perform this task, one for the production server and one for test servers in general.

	== Restarting the production ~~Vidjil~~ instance ==		== Restarting the Vidjil production instance ==
	* send an email to the users to let them know Vidjil will be undergoing a brief maintenance. User emails can be obtained by going to the users tab in the web application (https://vidjil.boldrini.org.br/).		* send an email to the users to let them know Vidjil will be undergoing a brief maintenance. User emails can be obtained by going to the users tab in the web application (https://vidjil.boldrini.org.br/).
	* access ~~via <code>ssh</code>~~ the Vidjil production server (<code>vidjil.boldrini.org.br</code>).		* access the Vidjil production server (<code>vidjil.boldrini.org.br</code>) via <code>ssh</code>.
	* go to the Vidjil Docker directory:		* go to the Vidjil Docker directory:
	<blockquote>		<blockquote>
Line 21:		Line 21:
	</blockquote>		</blockquote>
	* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</code> (all containers must be up) and by accessing the web application.		* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</code> (all containers must be up) and by accessing the web application.
	* send another email to the users, letting them ~~now~~ that the maintenance is finished and that Vidjil is back online.		* send another email to the users, letting them know that the maintenance is finished and that Vidjil is back online.

	== Restarting a generic Vidjil instance ==		== Restarting a generic Vidjil instance ==

Meidanis: replaced by


2023-12-06T20:58:25Z
</docker>  replaced by  <code>

				
				
				
				
				
				← Older revision
				Revision as of 20:58, 6 December 2023
				
Line 41:
Line 41:
<code>docker-compose -f docker-compose-wrapper.yml up -d</code> <code>docker-compose -f docker-compose-wrapper.yml up -d</code>
</blockquote> </blockquote>
* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application. * after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</code> (all containers must be up) and by accessing the web application.



Giusti: formatting
2023-12-06T12:37:10Z
formatting

				
				
				
				
				
				← Older revision
				Revision as of 12:37, 6 December 2023
				
Line 1:
Line 1:
Sometimes a Vidjil instance needs to be restarted, such as when the application is down or when you need to reload it for some reason. Another important aspect of performing a restart is whether or not the Vidjil instance in question is the production server. As such, below are presented two sets of instructions on how to perform this task, one for the production server and one for test servers in general. Sometimes a Vidjil instance needs to be restarted, such as when the application is down or when you need to reload it for some reason. Another important aspect of performing a restart is whether or not the Vidjil instance in question is the production server. As such, below are presented two sets of instructions on how to perform this task, one for the production server and one for test servers in general.



To restart the production Vidjil instance (https://vidjil.boldrini.org.br/): == Restarting the production Vidjil instance ==
* send an email to the users to let them know Vidjil will be undergoing a brief maintenance. User emails can be obtained by going to the users tab in the web application. * send an email to the users to let them know Vidjil will be undergoing a brief maintenance. User emails can be obtained by going to the users tab in the web application (https://vidjil.boldrini.org.br/).
* access via <code>ssh</code> the Vidjil production server (<code>vidjil.boldrini.org.br</code>). * access via <code>ssh</code> the Vidjil production server (<code>vidjil.boldrini.org.br</code>).
* go to the Vidjil Docker directory:   * go to the Vidjil Docker directory:
<blockquote>
<code>cd ~vidjil/code/2020-vidjil/docker</code> <code>cd ~vidjil/code/2020-vidjil/docker</code>
</blockquote>
* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down. * check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.
<blockquote>
<code>docker-compose ps</code> <code>docker-compose ps</code>
</blockquote>
* shut down the 5 containers: * shut down the 5 containers:
<blockquote>
<code>docker-compose -f docker-compose-wrapper.yml down</code> <code>docker-compose -f docker-compose-wrapper.yml down</code>
</blockquote>
* after the shut down is finished, restart the containers: * after the shut down is finished, restart the containers:
<blockquote>
<code>docker-compose -f docker-compose-wrapper.yml up -d</code> <code>docker-compose -f docker-compose-wrapper.yml up -d</code>
</blockquote>
* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</code> (all containers must be up) and by accessing the web application. * after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</code> (all containers must be up) and by accessing the web application.
* send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online. * send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online.



To restart a generic Vidjil instance: == Restarting a generic Vidjil instance ==
* access your Vidjil server. * access your Vidjil server.
* go to the Vidjil Docker directory.   * go to the Vidjil Docker directory.  
<blockquote>
<code>cd <path/to/vidjil>/docker</code> <code>cd <path/to/vidjil>/docker</code>
</blockquote>
* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down. * check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.
<blockquote>
<code>docker-compose ps</code> <code>docker-compose ps</code>
</blockquote>
* shut down the 5 containers: * shut down the 5 containers:
<blockquote>
<code>docker-compose -f docker-compose-wrapper.yml down</code> <code>docker-compose -f docker-compose-wrapper.yml down</code>
</blockquote>
* after the shut down is finished, restart the containers: * after the shut down is finished, restart the containers:
<blockquote>
<code>docker-compose -f docker-compose-wrapper.yml up -d</code> <code>docker-compose -f docker-compose-wrapper.yml up -d</code>
</blockquote>
* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application. * after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application.





Giusti: fix code tag
2023-12-06T12:31:48Z
fix code tag

				
				
				
				
				
				← Older revision
				Revision as of 12:31, 6 December 2023
				
Line 12:
Line 12:
* after the shut down is finished, restart the containers: * after the shut down is finished, restart the containers:
<code>docker-compose -f docker-compose-wrapper.yml up -d</code> <code>docker-compose -f docker-compose-wrapper.yml up -d</code>
* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application. * after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</code> (all containers must be up) and by accessing the web application.
* send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online. * send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online.








Giusti: no blockquote
2023-12-06T12:30:02Z
no blockquote

				
				
				
				
				
				← Older revision
				Revision as of 12:30, 6 December 2023
				
Line 5:
Line 5:
* access via <code>ssh</code> the Vidjil production server (<code>vidjil.boldrini.org.br</code>). * access via <code>ssh</code> the Vidjil production server (<code>vidjil.boldrini.org.br</code>).
* go to the Vidjil Docker directory:   * go to the Vidjil Docker directory:  
<blockquote> 
<code>cd ~vidjil/code/2020-vidjil/docker</code> <code>cd ~vidjil/code/2020-vidjil/docker</code>
</blockquote> 
* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down. * check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.
<blockquote> 
<code>docker-compose ps</code> <code>docker-compose ps</code>
</blockquote> 
* shut down the 5 containers: * shut down the 5 containers:
<blockquote> 
<code>docker-compose -f docker-compose-wrapper.yml down</code> <code>docker-compose -f docker-compose-wrapper.yml down</code>
</blockquote> 
* after the shut down is finished, restart the containers: * after the shut down is finished, restart the containers:
<blockquote> 
<code>docker-compose -f docker-compose-wrapper.yml up -d</code> <code>docker-compose -f docker-compose-wrapper.yml up -d</code>
</blockquote> 
* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application. * after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application.
* send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online. * send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online.
Line 26:
Line 18:
* access your Vidjil server. * access your Vidjil server.
* go to the Vidjil Docker directory.   * go to the Vidjil Docker directory.  
<blockquote> 
<code>cd <path/to/vidjil>/docker</code> <code>cd <path/to/vidjil>/docker</code>
</blockquote> 
* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down. * check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.
<blockquote> 
<code>docker-compose ps</code> <code>docker-compose ps</code>
</blockquote> 
* shut down the 5 containers: * shut down the 5 containers:
<blockquote> 
<code>docker-compose -f docker-compose-wrapper.yml down</code> <code>docker-compose -f docker-compose-wrapper.yml down</code>
</blockquote> 
* after the shut down is finished, restart the containers: * after the shut down is finished, restart the containers:
<blockquote> 
<code>docker-compose -f docker-compose-wrapper.yml up -d</code> <code>docker-compose -f docker-compose-wrapper.yml up -d</code>
</blockquote> 
* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application. * after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application.





Giusti: vidjil restart first commit
2023-12-06T12:19:42Z
vidjil restart first commit
New page
Sometimes a Vidjil instance needs to be restarted, such as when the application is down or when you need to reload it for some reason. Another important aspect of performing a restart is whether or not the Vidjil instance in question is the production server. As such, below are presented two sets of instructions on how to perform this task, one for the production server and one for test servers in general.



To restart the production Vidjil instance (https://vidjil.boldrini.org.br/):

* send an email to the users to let them know Vidjil will be undergoing a brief maintenance. User emails can be obtained by going to the users tab in the web application.

* access via <code>ssh</code> the Vidjil production server (<code>vidjil.boldrini.org.br</code>).

* go to the Vidjil Docker directory: 

<blockquote>

<code>cd ~vidjil/code/2020-vidjil/docker</code>

</blockquote>

* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.

<blockquote>

<code>docker-compose ps</code>

</blockquote>

* shut down the 5 containers:

<blockquote>

<code>docker-compose -f docker-compose-wrapper.yml down</code>

</blockquote>

* after the shut down is finished, restart the containers:

<blockquote>

<code>docker-compose -f docker-compose-wrapper.yml up -d</code>

</blockquote>

* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application.

* send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online.



To restart a generic Vidjil instance:

* access your Vidjil server.

* go to the Vidjil Docker directory. 

<blockquote>

<code>cd <path/to/vidjil>/docker</code>

</blockquote>

* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.

<blockquote>

<code>docker-compose ps</code>

</blockquote>

* shut down the 5 containers:

<blockquote>

<code>docker-compose -f docker-compose-wrapper.yml down</code>

</blockquote>

* after the shut down is finished, restart the containers:

<blockquote>

<code>docker-compose -f docker-compose-wrapper.yml up -d</code>

</blockquote>

* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application.

← Older revision		Revision as of 20:58, 6 December 2023
Line 41:		Line 41:
	<code>docker-compose -f docker-compose-wrapper.yml up -d</code>		<code>docker-compose -f docker-compose-wrapper.yml up -d</code>
	</blockquote>		</blockquote>
	* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</~~docker~~> (all containers must be up) and by accessing the web application.		* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</code> (all containers must be up) and by accessing the web application.

← Older revision		Revision as of 12:37, 6 December 2023
Line 1:		Line 1:
	Sometimes a Vidjil instance needs to be restarted, such as when the application is down or when you need to reload it for some reason. Another important aspect of performing a restart is whether or not the Vidjil instance in question is the production server. As such, below are presented two sets of instructions on how to perform this task, one for the production server and one for test servers in general.		Sometimes a Vidjil instance needs to be restarted, such as when the application is down or when you need to reload it for some reason. Another important aspect of performing a restart is whether or not the Vidjil instance in question is the production server. As such, below are presented two sets of instructions on how to perform this task, one for the production server and one for test servers in general.

	~~To restart~~ the production Vidjil instance ~~(https://vidjil.boldrini.org.br/):~~		== Restarting the production Vidjil instance ==
	* send an email to the users to let them know Vidjil will be undergoing a brief maintenance. User emails can be obtained by going to the users tab in the web application.		* send an email to the users to let them know Vidjil will be undergoing a brief maintenance. User emails can be obtained by going to the users tab in the web application (https://vidjil.boldrini.org.br/).
	* access via <code>ssh</code> the Vidjil production server (<code>vidjil.boldrini.org.br</code>).		* access via <code>ssh</code> the Vidjil production server (<code>vidjil.boldrini.org.br</code>).
	* go to the Vidjil Docker directory:		* go to the Vidjil Docker directory:
			<blockquote>
	<code>cd ~vidjil/code/2020-vidjil/docker</code>		<code>cd ~vidjil/code/2020-vidjil/docker</code>
			</blockquote>
	* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.		* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.
			<blockquote>
	<code>docker-compose ps</code>		<code>docker-compose ps</code>
			</blockquote>
	* shut down the 5 containers:		* shut down the 5 containers:
			<blockquote>
	<code>docker-compose -f docker-compose-wrapper.yml down</code>		<code>docker-compose -f docker-compose-wrapper.yml down</code>
			</blockquote>
	* after the shut down is finished, restart the containers:		* after the shut down is finished, restart the containers:
			<blockquote>
	<code>docker-compose -f docker-compose-wrapper.yml up -d</code>		<code>docker-compose -f docker-compose-wrapper.yml up -d</code>
			</blockquote>
	* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</code> (all containers must be up) and by accessing the web application.		* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</code> (all containers must be up) and by accessing the web application.
	* send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online.		* send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online.

	~~To restart~~ a generic Vidjil instance:		== Restarting a generic Vidjil instance ==
	* access your Vidjil server.		* access your Vidjil server.
	* go to the Vidjil Docker directory.		* go to the Vidjil Docker directory.
			<blockquote>
	<code>cd <path/to/vidjil>/docker</code>		<code>cd <path/to/vidjil>/docker</code>
			</blockquote>
	* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.		* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.
			<blockquote>
	<code>docker-compose ps</code>		<code>docker-compose ps</code>
			</blockquote>
	* shut down the 5 containers:		* shut down the 5 containers:
			<blockquote>
	<code>docker-compose -f docker-compose-wrapper.yml down</code>		<code>docker-compose -f docker-compose-wrapper.yml down</code>
			</blockquote>
	* after the shut down is finished, restart the containers:		* after the shut down is finished, restart the containers:
			<blockquote>
	<code>docker-compose -f docker-compose-wrapper.yml up -d</code>		<code>docker-compose -f docker-compose-wrapper.yml up -d</code>
			</blockquote>
	* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application.		* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application.

← Older revision		Revision as of 12:31, 6 December 2023
Line 12:		Line 12:
	* after the shut down is finished, restart the containers:		* after the shut down is finished, restart the containers:
	<code>docker-compose -f docker-compose-wrapper.yml up -d</code>		<code>docker-compose -f docker-compose-wrapper.yml up -d</code>
	* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</~~docker~~> (all containers must be up) and by accessing the web application.		* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</code> (all containers must be up) and by accessing the web application.
	* send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online.		* send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online.

← Older revision		Revision as of 12:30, 6 December 2023
Line 5:		Line 5:
	* access via <code>ssh</code> the Vidjil production server (<code>vidjil.boldrini.org.br</code>).		* access via <code>ssh</code> the Vidjil production server (<code>vidjil.boldrini.org.br</code>).
	* go to the Vidjil Docker directory:		* go to the Vidjil Docker directory:
	~~<blockquote>~~
	<code>cd ~vidjil/code/2020-vidjil/docker</code>		<code>cd ~vidjil/code/2020-vidjil/docker</code>
	~~</blockquote>~~
	* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.		* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.
	~~<blockquote>~~
	<code>docker-compose ps</code>		<code>docker-compose ps</code>
	~~</blockquote>~~
	* shut down the 5 containers:		* shut down the 5 containers:
	~~<blockquote>~~
	<code>docker-compose -f docker-compose-wrapper.yml down</code>		<code>docker-compose -f docker-compose-wrapper.yml down</code>
	~~</blockquote>~~
	* after the shut down is finished, restart the containers:		* after the shut down is finished, restart the containers:
	~~<blockquote>~~
	<code>docker-compose -f docker-compose-wrapper.yml up -d</code>		<code>docker-compose -f docker-compose-wrapper.yml up -d</code>
	~~</blockquote>~~
	* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application.		* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application.
	* send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online.		* send another email to the users, letting them now that the maintenance is finished and that Vidjil is back online.
Line 26:		Line 18:
	* access your Vidjil server.		* access your Vidjil server.
	* go to the Vidjil Docker directory.		* go to the Vidjil Docker directory.
	~~<blockquote>~~
	<code>cd <path/to/vidjil>/docker</code>		<code>cd <path/to/vidjil>/docker</code>
	~~</blockquote>~~
	* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.		* check the status of the Docker containers. Vidjil is composed by 5 containers, and when the application is down, usually at least one of the containers will also be down.
	~~<blockquote>~~
	<code>docker-compose ps</code>		<code>docker-compose ps</code>
	~~</blockquote>~~
	* shut down the 5 containers:		* shut down the 5 containers:
	~~<blockquote>~~
	<code>docker-compose -f docker-compose-wrapper.yml down</code>		<code>docker-compose -f docker-compose-wrapper.yml down</code>
	~~</blockquote>~~
	* after the shut down is finished, restart the containers:		* after the shut down is finished, restart the containers:
	~~<blockquote>~~
	<code>docker-compose -f docker-compose-wrapper.yml up -d</code>		<code>docker-compose -f docker-compose-wrapper.yml up -d</code>
	~~</blockquote>~~
	* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application.		* after the containers finish restarting, check if the service is indeed back online both by running <code>docker-compose ps</docker> (all containers must be up) and by accessing the web application.