Admin: Add Navbox deployment template before Related (via update-page on MediaWiki MCP Server)

2026-07-06T04:01:17Z

Add Navbox deployment template before Related (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 09:31, 6 July 2026
Line 305:		Line 305:

	For troubleshooting, feel free to join our Community on Slack at [<nowiki/>https://slack.ohc.network slack.ohc.network]. You may also refer to the official [<nowiki/>https://www.digitalocean.com/docs DigitalOcean Documentation] for any questions about DigitalOcean.		For troubleshooting, feel free to join our Community on Slack at [<nowiki/>https://slack.ohc.network slack.ohc.network]. You may also refer to the official [<nowiki/>https://www.digitalocean.com/docs DigitalOcean Documentation] for any questions about DigitalOcean.

			{{Navbox deployment}}

	{{Related}}		{{Related}}

Admin: OHC identity seed

2026-07-04T23:08:06Z

OHC identity seed

New page

{{Doc header
|type=guide
|domain=deployment
|title=Deploying Care on DigitalOcean
|order=4
}}

= Deploying Care on DigitalOcean =

In this guide, we'll walk you through deploying '''Care''' on '''DigitalOcean'''. We'll keep things simple so you can follow along to get your instance up and running. Expect the process to take about '''an hour''', depending on your familiarity with the tools.

For an overview of all supported cloud providers and their infrastructure requirements, see the [[Index|Cloud providers overview]].

-----

== Prerequisites ==

* A DigitalOcean account ([<nowiki/>https://www.digitalocean.com Sign up here]).
* A fork of the Care backend and frontend repositories.
* A registered domain name (optional but recommended).
* Basic familiarity with DigitalOcean's App Platform and Spaces.

-----

== What You'll Be Doing ==

* Set up a '''PostgreSQL database''' for secure data storage.
* Configure '''DigitalOcean Spaces''' for handling files and media.
* Deploy the '''Care backend''' with Redis and Celery for task management.
* Set up the '''Care frontend''' for user access.
* Secure the setup with custom domains, API keys, and SSL.
* Setup a CI/CD Pipeline for Continuous Deployment.

-----

== Step 1: Create the Database ==

=== 1.1 Navigate to Databases ===

* Log in to DigitalOcean and go to the '''Databases''' section.

=== 1.2 Create a PostgreSQL Database ===

<ul>
<li>Click '''Create Database'''.</li>
<li>Choose the following:
<ul>
<li>'''Region''': Select the nearest data center.</li>
<li>'''Engine''': PostgreSQL (Version 16).</li>
<li>'''Resources''': Select a plan based on your requirements.</li></ul>

![[Do db 1|Navigate to Databases]]
<ul>
<li>'''Name''': Give your database a unique name.</li>
<li>'''Tags''': Add tags for organization.</li></ul>

![[Do db 2|Navigate to Databases]]
![[Do db 3|Create Database]]</li></ul>

=== 1.3 Save Connection Details ===

<ul>
<li>Once the database is created, note the connection URL for later use.
![[Do db 4|Connection String]]</li></ul>

-----

== Step 2: Set Up Object Storage (Spaces) ==

=== 2.1 Navigate to Spaces ===

* Go to the '''Spaces''' section in DigitalOcean.

=== 2.2 Create a New Space ===

<ul>
<li>Click '''Create a Space'''.
![[Do spaces 1|Create Space]]</li>
<li>Choose:
<ul>
<li>'''Region''': Select the same region as your database.</li>
<li>'''Enable CDN''': For faster file delivery.</li>
<li>'''Bucket Name''': Enter a unique name.</li>
<li>'''Project''': Select the default project.</li>
<li>'''Create''': Click to create the space.</li></ul>

![[Do spaces 3|Create Space]]</li></ul>

=== 2.3 Generate API Keys ===

<ul>
<li>Go to the '''API''' tab and click '''Spaces Keys'''.</li>
<li>Create a new key pair and save the '''Key''' and '''Secret'''.
![[Do spaces 2|Generate Keys]]</li></ul>

-----

== Step 3: Deploy the Care Backend (BE) ==

=== Step 3.1: Deploy Redis ===

==== 3.1.1 Set Up Redis ====

<ul>
<li>Go to the App Platform and click '''Create App'''.
![[Do app 1|Select App Platform]]</li>
<li>Choose '''Docker Hub''' as the source and use:
<ul>
<li>'''Repository''': <code>redis/redis-stack-server</code>.</li>
<li>'''Tag''': <code>6.2.6-v10</code>.</li>
<li>'''Port''': Expose <code>6379</code> as an internal port.</li></ul>
</li>
<li>Name the component <code>redis</code>.
![[Redis 1|Select App Platform]]
![[Redis 2|Edit these fields]]</li></ul>

==== 3.1.2 Name and Deploy ====

<ul>
<li>Name the App <code>care-backend</code> and deploy it.
![[Redis 3|Name and Deploy]]</li></ul>

-----

=== Step 3.2: Deploy the Care Backend ===

==== 3.2.1 Fork and Clone the Repository ====

* Fork the [<nowiki/>https://github.com/ohcnetwork/care Care Backend Repository].
* Use the <code>production</code> branch for deployment.

==== 3.2.2 Set Up the App ====

<ul>
<li>Click '''Create App''' and choose '''From Source Code'''.</li>
<li>Select your forked repo and branch.</li>
<li>Set the build and run commands:
![[Care django 1|Create Resource from Source Code]]
![[Care django 2|Select GitHub Repository]]
<ul>
<li>'''Build Command:'''
<syntaxhighlight lang="bash">python install_plugins.py && python manage.py collectstatic --noinput && python manage.py compilemessages</syntaxhighlight></li>
<li>'''Run Command:'''
<syntaxhighlight lang="bash">gunicorn config.wsgi:application --workers 2 --bind :9000</syntaxhighlight>
![[Care django 3|Select GitHub Repository]]</li></ul>
</li></ul>

==== 3.2.3 Environment Variables ====

Add the following as global environment variables:

<syntaxhighlight lang="bash">DJANGO_SETTINGS_MODULE=config.settings.production
DATABASE_URL=<db-url> # Use the connection URL from Step 1.
REDIS_URL=redis://redis:6379
CORS_ALLOWED_ORIGINS=["https://care.example.com","http://localhost:4000","http://127.0.0.1:4000"]
CELERY_BROKER_URL=redis://redis:6379
REDIS_URL=redis://redis:6379
BUCKET_PROVIDER=DIGITAL_OCEAN
BUCKET_REGION=nyc3 # Use the region of your Spaces.
BUCKET_KEY= # Use the Spaces key.
BUCKET_SECRET= # Use the Spaces secret.
BUCKET_HAS_FINE_ACL=true
FILE_UPLOAD_BUCKET=example-space-ohc # Use the name of your Space.
FILE_UPLOAD_BUCKET_ENDPOINT=https://example-space-ohc.nyc3.digitaloceanspaces.com
FACILITY_S3_BUCKET=example-space-ohc # Use the name of your Space.
FACILITY_S3_BUCKET_ENDPOINT=https://example-space-ohc.nyc3.digitaloceanspaces.com
JWKS_BASE64= # Add your JWKS key. (Refer to the next section to create one.)
DISABLE_COLLECTSTATIC=1</syntaxhighlight>
===== Generate JWKS Key =====

The <code>JWKS_BASE64</code> value is generated here. Use the generator below to create a key, then paste the output into the <code>JWKS_BASE64</code> environment variable above.

<JwksGenerator />

==== 3.2.4 Expose Ports ====

* Expose port <code>9000</code> for public HTTP access.

-----

=== Step 3.3: Add a Domain for the Backend ===

==== 3.3.1 Configure Domain ====

<ul>
<li>Go to the app settings and add your domain (e.g., <code>care-api.example.com</code>).</li>
<li>Update your DNS provider with the CNAME record.
![[Domain|Add Domain]]</li></ul>

-----

=== Step 3.4: Set Up Celery Worker and Beat ===

==== 3.4.1 Celery Worker ====

<ul>
<li>Create a new component in the app.</li>
<li>Use the following '''Run Command''':
<syntaxhighlight lang="bash">celery --app=config.celery_app worker --max-tasks-per-child=2 --concurrency=2 --loglevel=DEBUG --logfile stdout</syntaxhighlight>
![[Worker 1|Celery Worker]]
![[Worker 2|Celery Worker]]</li></ul>

==== 3.4.2 Celery Beat ====

<ul>
<li>Create another component with the following '''Run Command''':
<syntaxhighlight lang="bash">python manage.py migrate</syntaxhighlight>
![[Job 1|Celery Job]]
![[Job 2|Celery Job]]</li></ul>

-----

== Step 4: Deploy the Care Frontend (FE) ==

=== 4.1 Fork the Frontend Repository ===

* Fork the [<nowiki/>https://github.com/ohcnetwork/care_fe Care Frontend Repository].
* Use the <code>production</code> branch.

=== 4.2 Set Up the App ===

<ul>
<li>Click '''Create App''' and configure:
<ul>
<li>'''Type''': Static Site.</li>
<li>'''Build Command:''' <code>npm run build</code>.</li>
<li>'''Environment Variable:'''
<syntaxhighlight lang="bash">REACT_CARE_API_URL=https://care-api.example.com</syntaxhighlight></li>
<li>'''Output Directory:''' Auto.</li></ul>
</li></ul>

=== 4.3 Add Domain ===

<ul>
<li>Go to the app settings and add the frontend domain (e.g., <code>care.example.com</code>).
![[Care fe 1|Frontend Setup]]
![[Care fe 2|Celery Job]]
![[Care fe 3|Celery Job]]</li></ul>

-----

== Step 5: Secure Database Access ==

=== 5.1 Restrict Access ===

<ul>
<li>Navigate to the Database settings.</li>
<li>Add the Care backend app as a trusted source.
![[Secure db|Secure Database]]</li></ul>

-----

== Step 6: Configure CORS for Spaces ==

=== 6.1 Go to Bucket Settings ===

<ul>
<li>Open your bucket in Spaces.</li>
<li>Add the following CORS configuration:
<syntaxhighlight lang="json">[
{
"AllowedHeaders": ["*"],
"AllowedMethods": ["GET", "POST", "PUT", "DELETE"],
"AllowedOrigins": ["https://example.com"],
"ExposeHeaders": []
}
]</syntaxhighlight>
![[Cors|CORS]]</li></ul>

-----

== Final Steps ==

<ul>
<li>'''Verify Deployment:'''
<ul>
<li>Test the backend and frontend by accessing the respective domains.</li>
<li>Ensure all components (Redis, Celery Worker, Beat) are running.</li></ul>
</li>
<li>'''Optimize Security:'''
<ul>
<li>Use SSL certificates (e.g., Let's Encrypt) to enable HTTPS.</li>
<li>Configure firewall rules to restrict access.
![[Care infra do|Care Infra]]</li></ul>
</li></ul>

-----

== Conclusion ==

You've successfully deployed the Care application on DigitalOcean! With the database, object storage, backend, and frontend configured, your application is ready for use. 🚀

For troubleshooting, feel free to join our Community on Slack at [<nowiki/>https://slack.ohc.network slack.ohc.network]. You may also refer to the official [<nowiki/>https://www.digitalocean.com/docs DigitalOcean Documentation] for any questions about DigitalOcean.

{{Related}}

Deployment/Providers/Deploying Care on DigitalOcean - Revision history

Admin: Add Navbox deployment template before Related (via update-page on MediaWiki MCP Server)

Admin: OHC identity seed