help with first-time shipping

[AnastasiaDv491]

Is your request related to a problem? Please describe. not a problem, we jsut want to ship something and not wait until the last week

Describe the solution you'd like server where we can ship

Describe alternatives you've considered Netlify ?

[jbelien]

Hello @osoc21/the-deloitted-spaghettis ,

No worries, I've got your back!

What do you need ? What's your stack ?

[AnastasiaDv491]

we need guidance in shipping i believe

[jbelien]

No worries ! I'll help you with the shipping ! 😃

I just need to know what are the "components" you're using in your front-end/back-end to choose the "best" deployment solution.

[AnastasiaDv491]

we are using vite project, svelte and tailwind css

back end: flask + python API + docker

[jbelien]

Perfect! 👍

I'll deploy your project using DigitalOcean App Platform:

• Back-end using your Dockerfile
• Front-end build statically

[jbelien]

Deployment is on its way! I'll let you know (here) when it's ready.

DigitalOcean App Platform configuration:

domains:
- domain: future-of-work.osoc.be
  type: PRIMARY
  zone: osoc.be
name: future-of-work
region: ams
services:
- dockerfile_path: /backend/Dockerfile
  github:
    branch: master
    repo: osoc21/Future-of-Work
  http_port: 4000
  instance_count: 1
  instance_size_slug: basic-xxs
  name: future-of-work
  routes:
  - path: /api
  source_dir: /backend
static_sites:
- build_command: npm run build
  environment_slug: node-js
  github:
    branch: master
    repo: osoc21/Future-of-Work
  name: future-of-work-app
  routes:
  - path: /
  source_dir: /frontend

[jbelien]

🚀 https://future-of-work.osoc.be/

For details, see configuration in previous commit: https://github.com/osoc21/technical-support/issues/15#issuecomment-883218905

"Autodeploy code changes" is now enabled. App (front-end + back-end) will be automatically redeployed each time you push to master branch.

Let me know if everything is working fine!

---

Side note: I've fixed your Dockerfile (see https://github.com/osoc21/Future-of-Work/commit/623ab67d923a3c92574eaf3b1602cdd9987c7924) and enabled a GitHub Actions workflow to check your Dockerfile is building correctly (see https://github.com/osoc21/Future-of-Work/actions/workflows/docker-image.yml)

[AnastasiaDv491]

so everytime we push to master, those changes will appear?

[jbelien]

so everytime we push to master, those changes will appear?

Exactly! 🎉

[AnastasiaDv491]

some things are on fire on our end we will try to check in on thursday sorry :(((

[AnastasiaDv491]

so we tried putting most of it on master. however there are problems with docker-file. we are not sure which version to use since you changed. would it be possible to have a call with you tmr to make sure we dont screw it up?:D

[jbelien]

I don't understand what you mean by "we are not sure which version to use since you changed."

Deployment uses:

• Front-end: npm run build from https://github.com/osoc21/Future-of-Work/tree/master/frontend/package.json
• Back-end: https://github.com/osoc21/Future-of-Work/blob/master/backend/Dockerfile

Ping me tomorrow morning for a call.

[AnastasiaDv491]

alright, thank you!

[archived-m]

@jbelien I'll run compose in a full-blown droplet instead if that's alright with you :). I'll take care of the initial deploy and webhook setup. Thanks!

[jbelien]

🚀

• IP address: 167.71.72.187

I'll delete the App Platform stuff and redirect future-of-work.osoc.be to the droplet.

[jbelien]

Domain name future-of-work.osoc.be is now pointing to 167.71.72.187