Hosting existing apps

If you already have an application that you would like to bring into Diploi, you can import it using GitHub.

---

How to Import an Existing App into Diploi

Diploi offers two ways to import projects, by selecting the repo you want to import from a list of available repositories in your GitHub account or by using the URL of a GitHub repo, either a public one or your own.

1. Start a new project

   

2. Then switch from “Start From Scratch” to the “Import Repository” tab

   

3. Now you can select the source code you want to import. You can either select a repository stored in your own GitHub account or use a URL to import a public repo.

   Note

   You can also import your own repositories via URL, as long as you have approved Diploi to have access to them or if they are public.

   

4. Once you have selected the repository you’ll import, click on the “Analyze Repository” button. Diploi will then look for the configuration files (package.json, ‘requirements.txt’, etc) and readme in your repository, to determine how to properly import your project to Diploi.

   

   The import system will run an automated analysis, and conclude if your project can be hosted on Diploi or not.

   

   Note

   In cases when Diploi can’t automatically host your imported app, the import result will notify you the reasons why it can’t be configured.

   

   If you need support to import projects, contact us via email or in Discord.

   Tip

   As mentioned before, any repository created using Diploi can be imported without additional configuration required.

   

5. After Diploi analyzes your repository, you’ll get a report which also tells you if you will need to do additional config work to properly host your application.

   

   The import system will generate a custom diploi.yaml file for your app, and you can also expand it by adding additional components and add-ons, like additional databases or services. For more about how to use the diploi.yaml file, click here.

   

6. Now you should have a development deployment running. If your project is not loading properly or fails to start, check the deployment logs.

   Tip

   Diploi uses default port configurations for all supported frameworks and databases, so if your application uses other ports, try first changing your ports to match the ones used by Diploi. You can find the default port config by opening the Dockerfile.dev from the remote development environment.

Other considerations

Run command config

By default, Diploi will use common run commands for development and staging/production deployments, so there might be some situations when your imported application might fail because your project uses different run commands. To handle these situations, you can either modify the Dockerfile and Dockerfile.dev created by diploi, or modify your app’s config to include the commands used by Diploi to run your application.

Importing an external public repository

When you can import a publicly available repository, which doesn’t belong to your GitHub account, you will have the option of creating a new repository in your account to store your code or start a project without a repository.

In case you choose to proceed without a repo, your project won’t be able to start a Production or Staging deployment, because Diploi creates a GitHub Action which takes care of creating a build of your project, which can be ran in Staging and Production.

Caution

You cannot add a repository to an existing project. If you need to import an application and link it to a new repository, you will need to go through the process of importing the app again and then create a new repository before launching the project.

For more information about the differences between projects with or without a repository, check this article going over their properties.

Importing an app from a repository you own

When you import from a repo you own, Diploi will use the same repository by default to store your code, so any changes you make to your project can be pushed to the same repository you imported from.

Currently, you can’t import a repository and save it in a new repository.

Note

Once you import an application, you will need to push the files that Diploi creates in your project directly to the main branch of your repository. This is needed because Diploi uses Docker in the background to host your application, and it uses a GitHub Action to generate a Docker build that can be used by Diploi.

Supported Applications

Although it is technically possible to import any application, not every app will work right away, and they might require additional work in order to run properly after you import them to Diploi.

You can import any application built with Diploi, or with any of these frameworks, databases, and technologies:

Components available

Supabase new

FastAPI new

n8n new

Laravel new

Flask new

Deno new

Next.js

Node.js

Bun

React + Vite

Astro

SvelteKit

Nue

Ghost

Hono

ASP.NET

Lovable

Blazor

Static Website

Django beta

Python beta

Add-ons available

PostgreSQL

MongoDB

Redis

MariaDB

MinIO

Note

You can modify your application’s tech stack from the diploi.yaml file.

Apps built on Diploi

Any application built on Diploi can be imported into a new project without any additional configuration. Diploi will provision any component and add-on specified in the diploi.yaml file, but with the caveat that any environment variables used in the project must then be set manually, since Diploi doesn’t store the project’s secrets on GitHub.

Note

Any changes to component and/or add-on identifiers and root folders can break the base configuration of a project imported, so remember to update any references that have changed.

Apps built on Lovable

If you built a project on Lovable, you can seamlessly import it to Diploi. All you need to do is sync your application on GitHub.

For Lovable projects using Supabase, you can use the open-source version of Supabase that is available on Diploi. You can add Supabase by adding the snippet to your diploi.yaml file.

 - name: Supabase
 identifier: supabase
 package: https://github.com/diploi/component-supabase#main

Paste the snippet within the components field in the diploi.yaml, usually found in the root of your project.

components:
 - name: Lovable
 ...

 - name: Supabase
 identifier: supabase
 package: https://github.com/diploi/component-supabase#main

If you would like a detailed walkthrough about how to import an application built with Lovable, click here to check our tutorial explaining how to do it. We also have a guide walkthrough explaining how to use Cursor for your imported Lovable app, which you can check by clicking here.

Tip

To add additional frameworks and databases to your imported Lovable app, add the components and add-ons you would like by modifying the diploi.yaml file. Click here for more information about how to do it.

Running Supabase Migrations after Importing a Lovable App

If you are using the Lovable project with Supabase, you’ll need to run the necessary migrations, which should be stored inside your Supabase folder, as migrations.

You can apply the migrations to your new Supabase instance by running the command supabase migration up from the development environment created when you import the project.

Tip

Besides npm, Diploi also supports yarn and pnpm as package managers.

For Python-based applications, currently we support uv, but you can also import apps that use venv and pip.