Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate from Vercel to Netlify #1

Open
4 tasks
zackkrida opened this issue Sep 24, 2020 · 5 comments
Open
4 tasks

Migrate from Vercel to Netlify #1

zackkrida opened this issue Sep 24, 2020 · 5 comments
Labels
💻 aspect: code Concerns the software code in the repository 🤖 aspect: dx Concerns developers' experience with the codebase 🌟 goal: addition Addition of new feature ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟧 priority: high Stalls work on the project or its dependents 🏁 status: ready for work Ready for work

Comments

@zackkrida
Copy link
Member

Holy cloud providers! We should switch this from Vercel to Netlify, so we can use Creative Common's Netlify account. Currently this is on my personal Vercel account (which I don't mind at all) but before this is adopted by any of our web properties it should be moved to a CC-owned account.

The serverless functions here require a paid account in Vercel, due to their execution durations and memory usage. I am not sure what will be necessary on Netlify.

The main thing we'll need to do is restructure the serverless functions to the style used by Netlify. Vercel uses a pretty simple, but bespoke signature for each serverless function:

import { IncomingMessage, ServerResponse } from 'http';

export default async function handler(req, res) {
	 // your server-side functionality
}

Netlify serverless functions, by contrast, use the same signature as AWS Lamda functions:

exports.handler = function(event, context, callback) {
    // your server-side functionality
}

So to migrate to netlify we'll need to:

  • Research resource limits on Vercel / Netlify and if there's any new charges or limitations on Netlify
  • Move code to match Netlify's required code structure
  • Modify all serverless functions to match Netlify's function signature
  • Make any modifications necessary for TypeScript on Netlify (may not require anything—I haven't researched this yet)
@zackkrida zackkrida added help wanted Open to participation from the community Great Contribution 🟧 priority: high Stalls work on the project or its dependents 🏁 status: ready for work Ready for work 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🌟 goal: addition Addition of new feature ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🤖 aspect: dx Concerns developers' experience with the codebase labels Sep 24, 2020
@zackkrida zackkrida removed the 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work label Sep 24, 2020
@rajat2502
Copy link
Contributor

Hey @zackkrida, first of all, I would like to say that this is an awesome application. I really liked the concept of having an OG Image generator.
I would like to work on this one but I am not sure if I will be able to understand the code/implementation. Can you please share some resources/files that I should read before working on this.

@dhruvkb
Copy link
Member

dhruvkb commented Oct 11, 2020

Hey @rajat2502, both Netlify and Vercel have fantastic docs. I recommend reading the Netlify file-based config docs and the Vercel configuration docs so that you understand how to replace the vercel.json file with the corresponding netlify.toml file in the root of the project.

@dhruvkb
Copy link
Member

dhruvkb commented Oct 11, 2020

The steps after the file change would require access to CC's Netlify account so @zackkrida or I will take over from there.

@rajat2502
Copy link
Contributor

Okay thanks, @dhruvkb, I will go through these docs and then work on this issue.

@Kimbohlovette
Copy link

Kimbohlovette commented Nov 3, 2023

Hello @zackkrida is anyone currently working on this issue?
I would like to work on it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🤖 aspect: dx Concerns developers' experience with the codebase 🌟 goal: addition Addition of new feature ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟧 priority: high Stalls work on the project or its dependents 🏁 status: ready for work Ready for work
Projects
Status: Backlog
Development

No branches or pull requests

6 participants