open summer of code
HomeWebsiteGitHub
  • Welcome to osoc!
  • Code of Conduct
  • The osoc Way of Work & Play
    • Working Together in a Remote Setting
  • Students
    • Applying as a student at osoc
      • Privacy Policy for Open Knowledge Belgium
    • Being a student at osoc
      • Practical: When, where, how long, food
      • Health, COVID, Insurance, Sick Days
      • Study material
    • The Student Job
    • Salary & Reimbursements
  • Coaches & Student coaches
    • Being a coach at oSoc
    • The Coaching Job
      • Soft Skills & Expectations
      • Tasks
      • How to Manage a Team: Techniques
      • Coaching Cases
      • Battle Prep
      • Student Coaches
      • Screening students
    • Projects
    • Partner Communication
    • Practical
  • partners
    • Being a partner at oSoc
      • Apply
      • Attend
    • The Partner's Job
    • Projects
  • Tools & Resources
    • Discord
      • Basics
      • Discord etiquette
      • Setting your nickname & description
      • Managing notifications
      • Offering and Receiving Help
      • Find Your Discord Username
    • NextCloud
    • The #osoc Emoji
    • Big Blue Button: Video Calls
    • Deployment
    • Maps & Cartography
  • Tutorials
    • Create Crests
    • Pitching
      • Pitch and Interview Tips
      • Pitch on Discord
      • Pitch Content Tips
    • Interviews
    • Hosting
    • Deliver Like a Pro
      • Publish a Github Page
    • Conduct (Remote) Tests and Interviews with Real People + Archetypes
  • Organisers
    • How to set up oSoc for your country
      • Preparation
      • Selection
      • Practical
        • Setting Up a Remote Edition
      • Informing people
    • On-site editions: 4 weeks of well-organised serendipity
      • Calendar Example Remote Edition (BE)
        • Week 1: Explore
          • Day 1: Welcome (to the Madness 😏)
          • Day 2: Meet the Client + Prepare for Hackathon
          • Day 3: Hackathon & Pitching
          • Day 4: Pitch & Battle Plan
        • Week 2: Build
          • Day 1: Build, test, document + Learn how to vlog
          • Day 2: Build, test, document
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 3: Build more
          • Day 1: Build, test, document + How to deploy
          • Day 2: Day off!
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 4: Deliver
          • Day 1: Ship ship ship
          • Day 2: Pitch pitch pitch
          • Day 3: Delivery Day
          • Day 4: Demo Day
      • Kick-off day 1 (or chaos day)
      • Hackathon day 2 — 4
      • Build — week 2
      • Build — week 3
      • Delivery week — week 4
      • Evaluation — follow-up
    • Taking over the world
    • Salary & Reimbursements
    • Managing teams
  • test
Powered by GitBook
On this page
  • Hosting
  • Static website
  • Docker container(s)
  • Server / Droplet
  • Domain name
  • Sub-domain *.osoc.be
  • Domain name

Was this helpful?

  1. Tools & Resources

Deployment

How to deploy and host your project ?

PreviousBig Blue Button: Video CallsNextMaps & Cartography

Last updated 2 years ago

Was this helpful?

Hosting

Static website

Most projects can be built as a static website.

In this case, we recommend using platforms that can deploy your website for free.

Here are a few suggestions, but feel free to deploy your website using another solution:

Even though, it's possible to use GitHub Pages to deploy your project, we recommend not to use it because it will be used to deploy the page to present your project (during Week 4).

Example:

Contact you coach or osoc technical support if you need help to deploy your static website.

Docker container(s)

Some projects need something a bit more complicated. For instance, you need to deploy your own API and the front-end.

Your Docker container(s) will be deployed using .

Documentation:

⚠️ Digital Ocean App Platform does not support Docker Composer.

Contact you coach or osoc technical support if you need help to create the Docker container or deploy your Docker container.

Server / Droplet

If creating a Docker container is not option, we can give you root access to a Debian/Ubuntu server dedicated to your project and hosted in OKBE infrastructure.

This solution is not recommended and will have to be discussed with osoc technical support and OKBE infrastructure manager.

  • Memory: 1GB

  • CPU: 1vCPU

  • Transfer: 1TB

  • SSD: 25GB

Domain name

Sub-domain *.osoc.be

We offer an osoc.be sub-domain name for your project. We usually create a sub-domain name with the name of your project : your-team-name.osoc.be

If your project needs multiple sub-domains, it's of course possible!

Example:

  • your-team-name.osoc.be for the front-end

  • api.your-team-name.osoc.be for the API

  • ...

Once your project is deployed, contact osoc technical support with the IP address or CNAME record, so we can create the sub-domain name and link it to your project.

Domain name

This server will be a with the following setup:

We do not offer domain names but if your client offers a domain name (example from a previous year: ), give your client the IP address or CNAME record so they can configure the domain name correctly.

https://docs.netlify.com/welcome/add-new-site/
https://devcenter.heroku.com/articles/github-integration
https://vercel.com/docs/concepts/deployments/overview
https://osoc21.github.io/BikeInfrastructure/
Digital Ocean App Platform
https://docs.digitalocean.com/products/app-platform/
https://docs.digitalocean.com/products/app-platform/reference/dockerfile/
Digital Ocean Droplet
https://docs.netlify.com/domains-https/custom-domains/configure-external-dns/
https://devcenter.heroku.com/articles/custom-domains
https://vercel.com/docs/concepts/projects/custom-domains
https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages
https://routeplanner.bike.brussels/