added warning banner to outdated postgresql blog post
This commit is contained in:
@@ -1,3 +1,9 @@
|
||||
<div class="callout-warning">
|
||||
<p><b>Note</b>: as I'm constantly learning new things, this blog post is sort of outdated now. The information is still correct, but it feels inefficient and leads into a dead-end. I dislike this, as I wanted to write a guide that provides an expandable base. Therefore, I'll likely either update or replace this article and trim it down to focus on the important bits.</p>
|
||||
|
||||
<p>Expect a Go API.</p>
|
||||
</div>
|
||||
|
||||
*Hey!*
|
||||
|
||||
Do you want to develop a web application in SvelteKit? Do you want this application to access a PostgreSQL database on a remote server? Do you struggle with CORS (cross-origin resource sharing) and CSRF (cross-site request forgery) and keep receiving error 403? Well, I did, and I couldn't find ***ANYTHING*** on the internet going beyond a test running locally. This is why I'm writing this guide.
|
||||
|
||||
Reference in New Issue
Block a user