Back
Similar todos
Got my frontend app deployed to Netlify, it was surprisingly easy. Changed my Cloudflare DNS settings for the domain to point to Netlify, and turned off the 'Proxy' setting in Cloudflare. Changed my frontend and backend code to use the new setup of having the api at a different domain instead of at `/api/` at the same domain. Tomorrow I'll need to test that local development is still working properly and then see if I can get it working on Netlify/DigitalOcean.
Continuing to try to get Dokku working with a monorepo; I think I got past my last problem of how to deploy both apps by running on the server `dokku builder:set backend-app build-dir backend` (and similar for the frontend); now I'm seeing a new error when I try to deploy the frontend app: `Two different lockfiles found: package-lock.json and yarn.lock`; I seemed to fix it by deleting the yarn.lock. New error: "Missing script: start"; fixed that by adding a 'start' entry to my package.json. New error: "Cannot find module '@vitejs/plugin-vue'"; maybe because it's listed as a devDependency? I found this SO post where the guy said he ended up just putting his frontend on Netlify, so maybe I'll try that instead: stackoverflow.com/a/62455021/… ChatGPT is saying the way to do it is to deploy my API at api.mydomain.com and then direct traffic at other subdomains to Netlify to handle frontend requests. So I'll try that tomorrow.
Continuing to look into the CORS error I'm getting when my frontend tries to make an API request to my backend; it seems my backend dokku app wasn't deployed for some reason; destroyed my existing go dokku app and recreated it and then struggled with an error for a while before realizing I had the same issue a few days ago and the solution was to run `dokku builder:set backend-app build-dir backend`; now getting an error saying the download for my specified version of Go is "unknown to the buildpack"; after much trial-and-error I realized the problem was that Dokku has a stupid error message that makes it sound like it has already automatically chosen a Go buildpack when in fact it has not. I was additionally getting confused because I was seeing Dokku installing Go and not realizing that was because of my +heroku instruction in my go.mod file rather than Dokku automatically using a Go buildpack. The solution was to specify a Go buildpack for my app with `dokku buildpacks:add <my-app> heroku/go`. Now getting a new error: "Failed to connect to database". Fixed it by switching my code to use the `DATABASE_URL` environment variable that Dokku creates for your code to connect to the db. My `git push dokku main` finally succeeded, but I'm still getting a CORS error. Eventually figured out it was because my Dokku app name was `whatdo-backend` when I had forgotten that that would also be the name of the subdomain, so I had to delete the app and recreate it with the name `api`. I also created a `/ping` health-check URL to help me debug this more quickly. I'm now getting a 521 error, I think maybe because Dokku is running on http and Cloudflare is reaching out via https?
Messing around with cors proxies all day to get data from a gov public endpoint that's blocked by cors/csp. Tried Github's Flat Data too (that uses GH Actions). Didn't manage to solve it. Might try Cloudflare Workers using cloudflare-cors-anywhere instead. #uvindexsg #socialimpactpatronage
Got my personal website (nathanwailes.com) being served by Netlify after destroying the Digital Ocean droplet that was hosting it (just an index.html file)...got the welcome YouTube video working again, I guess YouTube requires some new iframe attrs now before it'll allow it to be played...bought a new domain (wailesgroup.com) for $10 and set it up on Netlify with a copy of my nw.com domain, I'm thinking of trying to start doing cold-emailing to get work as an agency / remote-worker management consultancy b/c I think the current agency I'm working for is billing my time at a way higher rate than I'm getting paid...spent a few minutes thinking about and adding Jira tickets for what I should work on next for that project (not today)...spent some time studying the [hnjobs GitHub repo][1] to see how it worked, to use it as a stepping stone towards automating applying to HN jobs...spent some more time thinking about trying to do interviews with YouTubers, I'm now thinking it may not be so useful, as I don't have a product I'm trying to sell right now, it's unlikely to have any lasting impact, and it would probably be a one-time thing... [1]: github.com/nchelluri/hnjobs/
got my personal website (nathanwailes.com/, just an index.html) working on a new $4/mo DO droplet that I intend to move everything over to while switching backends from Python to Go, nginx is way easier than Apache so far. Switched my personal site to use GitHub version control.
(continuation from last night) I set up a new DO box so I can basically serve an infinite number of static websites from for $5 a month. GitHub Pages have served me well but Cloudflare charge $20 or $30 to add more redirects (annoying) and GH's terms are for-profit friendly
Able to ssh into my new Digital Ocean droplet with my new 'nathan' user; installed nginx; updated my Cloudflare DNS records for my domains to point to my new droplet; deleted unused subdomains and old MX/TXT/CNAME records; confirmed a 'Hello World' index.html site served by nginx is working.
🤩 nextjs + github action + droplet + cloudflare
Decided to f it and just deploy the rough version first. Will add domain later, and task logs to come - jasonleowdotcom.netlify.app/ #indiejourney #jasonleowdotcom
Finish my initial test of self-hosted PaaS solutions and post about it on X: x.com/ben_makes_stuff/status/…
Next up: moving 
#unblockdomains to Dokku as a test and blogging about it !private
Finally got the Dokku Ruby on Rails example app working 😭 Apparently I just needed to reboot the droplet? `curl` to my droplet's IP wasn't working, `dokku ports:list ruby-getting-started` didn't show it listening on port 80, `dokku ports:add ruby-getting-started http:80:5000` resulted in an error saying nginx wasn't running. Rebooting seemed to fix it. Next up is trying to deploy my Go backend with Dokku. Destroyed the ruby demo dokku app. Resized my DO droplet to the $6/mo one.
new "works in public" blog (aka follow along) for DPP working on netlify with ssl after some tweaks. 
#downpayment
move domain from cloudflare to prepare for new https github features #dailyvibes
🚚 setup 
#deploy domain to point to Cloudflare in case I decide to release it
put frontend on netlify #gq
Deploying my first cloudflare worker. I found this way easier than trying to shoehorn everything into my VPS.
Continuing to try to get my dokku API to work, looking into an `ERR_CONNECTION_REFUSED` error. I posted for help on the dokku github: github.com/dokku/dokku/issues… I suspect the issue may be caused by my not having SSL set up but I'm not sure. I can't even find the logs where the refused connection is being logged.