Build your website with AI and put it online with Hodi

Where do I start?

Starting from scratch? A Hodi hosting plan, a GitHub account, a site generated with Lovable, connected to Hodifly. One afternoon is enough.

Already have an AI-generated site elsewhere? Push it to GitHub, open a Hodi hosting plan, connect Hodifly. That's all.

👉 Give https://hodifly.app/llms.txt to your AI: it will know how to use Hodifly to its fullest potential.

1. Building the site with AI

Which tools should I use?

We only list tools that can push your code to GitHub. That is the requirement for hosting it yourself afterwards (see §2).

• Lovable: the simplest option if you are not a developer. You describe your site and watch it being built live. Built-in GitHub connection.
• Bolt.new: same idea, very fast for a first prototype. One-click push to GitHub.
• v0 (Vercel): design-focused, excellent for good-looking pages. GitHub sync.
• Claude Code: for technical profiles and agencies. Works directly in your files and handles GitHub on its own.
• Cursor: an AI-assisted code editor, useful for picking up an existing project.

In short: you don't code → Lovable or Bolt. You or your provider codes → Claude Code or Cursor.

Is AI-generated code reliable?

For a brochure site, a catalogue or an internal tool: yes. For an application handling payments or sensitive data: have a human review it. AI writes code that works, not necessarily code that is secure.

How do I phrase my requests?

A good request contains four things:

1. Context: "Brochure site for an accounting firm in Abidjan, 5 pages."
2. The request: "Add a Contact page with a name / email / message form."
3. The constraint: "Without adding any new library."
4. The expected result: "A confirmation message must appear after sending."

Compare that with "make me a contact page". Precision up front saves you ten rounds of corrections later.

Any other advice?

Work in small steps. One request, check it, save it, move to the next. One big request produces something nobody can fix afterwards.

2. GitHub: the mandatory step

What is GitHub?

An online storage space for code that keeps every successive version of your files.

Picture a Google Drive that, on every save, keeps the previous version along with the date and the reason for the change. You can go back to yesterday's state, last week's, or day one, in seconds.

It is free, and your projects can stay private.

Are Git and GitHub the same thing?

No. Git is the software that manages versions. GitHub is the website that hosts your Git projects. Git is the engine, GitHub is the garage.

The five words you need

That is enough to get started. You will pick up the rest if you ever need it.

Why is it essential?

Three reasons:

1. You can go back. The AI will break something eventually. With GitHub, you recover the version that worked. Without it, you start over.
2. It is where deployment starts. Hodifly pulls your code from GitHub. No repository, no automatic deployment.
3. Your code belongs to you. If the AI platform shuts down or raises its prices, your site is already yours.

How do I create my account and my project?

1. Go to github.com → Sign up. It is free.
2. Turn on two-factor authentication (2FA) straight away.
3. Click New repository.
4. Give it a name with no spaces or accents (my-company-site) and tick Private.
5. Create repository. Done.

Do I have to type commands?

Not if you use Lovable, Bolt or v0. These tools push your code to GitHub in one click, once you have granted access.

And with Claude Code, you can simply ask: "save this and push it to GitHub".

What must never go on GitHub?

• Passwords and database credentials
• API keys (Stripe, Supabase, mail services…)
• .env files
• Your customers' data

These belong in your hosting configuration, never in the code.

⚠️ A key published on GitHub is compromised, even if you delete it afterwards. It stays in the history, and bots scan GitHub continuously. The only correct response is to rotate the key.

3. Hodifly: putting the site online

What is Hodifly?

Hodifly publishes your site straight from GitHub or GitLab, the way Netlify does, but on Hodi servers, in the country of your choice.

You connect it once. After that, every change pushed to your Git goes live automatically. No FTP, no files to transfer by hand.

Hodifly is included with Hodi web hosting plans.

How does it work?

1. Connect to your cPanel.
2. Launch Hodifly.
3. Connect your GitHub account, then pick your repository.
4. Choose the branch to publish (usually main).
5. Enter the domain or subdomain.
6. Deploy. The SSL certificate is installed automatically.

From then on, every push to GitHub updates the site by itself.

👉 Learn more

My Lovable site uses Supabase. Does that work?

Yes. Your site is hosted with Hodi and keeps talking to Supabase.

One caveat: if your Supabase instance sits in Europe or the United States, your data stays there. If data location matters to you (public tenders, personal data, local regulation), we can host your database in the same datacenter as your site.

👉 Moving from Supabase to a database hosted with Hodi

The deployment failed. What now?

1. Open the error log in Hodifly. The cause is written there.
2. Paste that log into your AI. This is exactly what it is good at.
3. Check that your API keys are set on the Hodi side (they are not on GitHub, and that is normal).

4. Why not just stay on the AI platform?

Speed. A site hosted in the United States and visited from Abidjan, Nairobi or Antananarivo travels thousands of kilometres. Hosted close to your visitors, it responds far faster.

Your data. Depending on your sector and your country, data location is not a detail. It is sometimes an obligation. Hodi operates in Tier III datacenters across more than 20 countries and territories, in Africa and in Europe.

Your independence. An AI platform is a good workshop, not a good warehouse. With GitHub + Hodifly, you can switch tools tomorrow without rebuilding anything.

The price. Platforms bill hosting separately, often based on usage, so unpredictably. Hodi hosting is a fixed price and even includes your domain name and mailboxes.

5. Before you publish: the checklist

• No passwords or keys in the code
• GitHub repository set to private, two-factor authentication enabled
• Tested on a real phone, not just in the preview
• Form protected against spam
• Legal notice and privacy policy (AI always forgets these)
• Page title, description and favicon filled in
• Images compressed. AI loves 4 MB photos. PageSpeed in cPanel can help you
• Automatic redirect to HTTPS. AutoSSL in cPanel can do it for you

Updated on: 28/07/2026