Latest static site news

static site

LXer: 3 Best Free and Open Source Awk Static Site Generators

By www.linuxquestions.org
Published On :: Mon, 30 Sep 2024 10:30:43 GMT

Published at LXer: There are lots of other advantages of running a full, static HTML website. We pick the finest Awk-based tools. Read More......

Full Article

Syndicated Linux News

static site

Kinsta Unveils High-Performance Platform for Free Static Site Hosting

By www.24-7pressrelease.com
Published On :: Thu, 19 Oct 2023 08:00:00 GMT

The premium cloud hosting provider adds static site hosting to its services, which also include WordPress, application, and database hosting

Full Article

static site

Should you use Userbase for your next static site?

By feedproxy.google.com
Published On :: Wed, 06 May 2020 08:00:00 -0400

During the winter 2020 Pointless Weekend, we built TrailBuddy (working app coming soon). Our team consisted of four developers, two project managers, two front-end developers, a digital-analyst, a UXer, and a designer. In about 48 hours, we took an idea from Jeremy Field’s head to a (mostly) working app. We broke up the project in two parts:. First, a back-end that crunches trail, weather, and soil data. That data is exposed via a GraphQL API for a web app to consume.

While developers built the API, I built a static front end using Next.js. Famously, static front-ends don’t have a database, or a concept of “users.” A bit of functionality I wanted to add was saving favorite trails. I didn’t want to be hacky about it, I needed some way to add users and a database. I knew it’d be hard for the developers to set this up as part of the API, they had their hands full with all the #soil-soil-soil-soil-soil (a slack channel dedicated solely to figuring out our soil data problem—those were plentiful.) I had been looking for an excuse to use Userbase, and this seemed like as good a time as any.

A textbook Userbase use case

“When would I use it?” The Usebase site lists these reasons:

If you want to build a web app without writing any backend code.
If you never want to see your users' data.
If you're tired of dealing with databases.
If you want to radically simplify your GDPR compliance.
And if you want to keep things really simple.

This was a perfect fit for my problem. I didn’t want to write any more backend code for this. I didn’t want to see our user’s data, I don’t care to know anyone’s favorite trails.* A nice bonus to not having users in our backend was not having to worry about keeping their data safe. We don’t have their data at all, it’s end-to-end encrypted by Userbase. We can offer a reasonable amount of privacy for free (well for the price of using Userbase: $49 a year.) I am not tired of dealing with databases, but I’d rather not. I don’t think anyone doesn’t want to simplify their GDPR compliance. Finally, given our tight timeline I wanted nothing more than to keep things really simple.

A sign up form that I didn't have to write a back-end for

Using Userbase

Userbase can be tried for free, so I set aside thirty minutes or so to do a quick proof of concept to make sure this would work out for us. I made an account and followed their Quickstart. Userbase is a fundamentally easy tool to use, but their quickstart is everything I’d want out of a quickstart:

Written in the most vanilla way possible (just HTML and vanilla JS). This means I can adapt it to my needs, in this case React using Next.js
Easy to follow, it does the most barebones tour of the functionality you can expect to get out of the SDK (software development kit.) In other words it is quick and it is a start
It has a live demo and code samples you can download and run yourself

It didn’t take long after that to integrate Userbase into our app with more help from their great docs. I debated whether to add code samples of what we did here, and I didn’t because any reader would be better off using the great quickstart and docs Userbase provides—they are that clear, and that good. Depending on your use case you’ll need to adapt the examples to your needs, for us the trickiest things were creating a top level authentication context to manage users in the app, and a custom hook to encapsulate all the logic for setting, updating, and deleting favourite trails in the app. Userbase’s SDK worked seamlessly for us.

A log in form that I didn't have to write a back-end for

Is Userbase for you?

Maybe. I am definitely a fan, so much so that this blog post probably reads like an advert. Userbase saved me a ton of time in this project. It reminded me of “The All Powerful Front End Developer” talk by Chris Coyer. I don’t fully subscribe to all the ideas in that talk, but it is nice to have “serverless” tools like Userbase, and all the new JAMstacky things. There are limits to the Userbase serverless experience in terms of scale, and control. Obviously relying on a third party for something always carries some (probably small) risk—it’s worth noting Usebase includes a note on their pricing page that says “You can host it yourself always under your control, or we can run it for you for a full serverless experience”—Still, I wouldn’t hesitate this to use in future projects.

One of the great things about Viget and Pointless Weekend is the opportunity to try new things. For me that was Next.js and Userbase for Trailbuddy. It doesn’t always work out (in fact this is my first pointless weekend where a risk hasn’t blown up in my face) but it is always fun. Getting to try out Userbase and beginning to think about how we may use it in the future made the weekend worthwhile for me, and it made my job on this project much more enjoyable.

*I will write a future post about privacy conscious analytics in TrailBuddy when I’ve figured that out. I am looking into Fathom Analytics for that.

Full Article

Code
Front-end Engineering

static site

Should you use Userbase for your next static site?

By feedproxy.google.com
Published On :: Wed, 06 May 2020 08:00:00 -0400

A textbook Userbase use case

“When would I use it?” The Usebase site lists these reasons:

If you want to build a web app without writing any backend code.
If you never want to see your users' data.
If you're tired of dealing with databases.
If you want to radically simplify your GDPR compliance.
And if you want to keep things really simple.

A sign up form that I didn't have to write a back-end for

Using Userbase

Written in the most vanilla way possible (just HTML and vanilla JS). This means I can adapt it to my needs, in this case React using Next.js
Easy to follow, it does the most barebones tour of the functionality you can expect to get out of the SDK (software development kit.) In other words it is quick and it is a start
It has a live demo and code samples you can download and run yourself

A log in form that I didn't have to write a back-end for

Is Userbase for you?

*I will write a future post about privacy conscious analytics in TrailBuddy when I’ve figured that out. I am looking into Fathom Analytics for that.

Full Article

Code
Front-end Engineering

static site

Should you use Userbase for your next static site?

By feedproxy.google.com
Published On :: Wed, 06 May 2020 08:00:00 -0400

A textbook Userbase use case

“When would I use it?” The Usebase site lists these reasons:

If you want to build a web app without writing any backend code.
If you never want to see your users' data.
If you're tired of dealing with databases.
If you want to radically simplify your GDPR compliance.
And if you want to keep things really simple.

A sign up form that I didn't have to write a back-end for

Using Userbase

Written in the most vanilla way possible (just HTML and vanilla JS). This means I can adapt it to my needs, in this case React using Next.js
Easy to follow, it does the most barebones tour of the functionality you can expect to get out of the SDK (software development kit.) In other words it is quick and it is a start
It has a live demo and code samples you can download and run yourself

A log in form that I didn't have to write a back-end for

Is Userbase for you?

*I will write a future post about privacy conscious analytics in TrailBuddy when I’ve figured that out. I am looking into Fathom Analytics for that.

Full Article

Code
Front-end Engineering

static site

Should you use Userbase for your next static site?

By feedproxy.google.com
Published On :: Wed, 06 May 2020 08:00:00 -0400

A textbook Userbase use case

“When would I use it?” The Usebase site lists these reasons:

If you want to build a web app without writing any backend code.
If you never want to see your users' data.
If you're tired of dealing with databases.
If you want to radically simplify your GDPR compliance.
And if you want to keep things really simple.

A sign up form that I didn't have to write a back-end for

Using Userbase

Written in the most vanilla way possible (just HTML and vanilla JS). This means I can adapt it to my needs, in this case React using Next.js
Easy to follow, it does the most barebones tour of the functionality you can expect to get out of the SDK (software development kit.) In other words it is quick and it is a start
It has a live demo and code samples you can download and run yourself

A log in form that I didn't have to write a back-end for

Is Userbase for you?

*I will write a future post about privacy conscious analytics in TrailBuddy when I’ve figured that out. I am looking into Fathom Analytics for that.

Full Article

Code
Front-end Engineering

static site

A simple Git deployment strategy for static sites

By nicolasgallagher.com
Published On :: Wed, 01 Jan 2014 16:00:00 -0800

This is how I am deploying the build of my static website to staging and production domains. It requires basic use of the CLI, Git, and SSH. But once you’re set up, a single command will build and deploy.

TL;DR: Push the static build to a remote, bare repository that has a detached working directory (on the same server). A post-receive hook checks out the files in the public directory.

Prerequisites

A remote web server to host your site.
SSH access to your remote server.
Git installed on your remote server (check with git --version).
Generate an SSH key if you need one.

On the server

Set up password-less SSH access

First, you need to SSH into your server, and provide the password if prompted.

ssh user@hostname

If there is no ~/.ssh directory in your user’s home directory, create one: mkdir ~/.ssh.

Next, you need to copy your public SSH key (see “Generate an SSH key” above) to the server. This allows you to connect via SSH without having to enter a password each time.

From your local machine – assuming your public key can be found at ~/.ssh/id_rsa.pub – enter the following command, with the correct user and hostname. It will append your public key to the authorized_keys file on the remote server.

ssh user@hostname 'cat >> ~/.ssh/authorized_keys' < ~/.ssh/id_rsa.pub

If you close the connection, and then attempt to establish SSH access, you should no longer be prompted for a password.

Create the remote directories

You need to have 2 directories for each domain you want to host. One for the Git repository, and one to contain the checked out build.

For example, if your domain were example.com and you also wanted a staging environment, you’d create these directories on the server:

mkdir ~/example.com ~/example.git

mkdir ~/staging.example.com ~/staging.example.git

Initialize the bare Git repository

Create a bare Git repository on the server. This is where you will push the build assets to, from your local machine. But you don’t want the files served here, which is why it’s a bare repository.

cd ~/example.git
git init --bare

Repeat this step for the staging domain, if you want.

Write a post-receive hook

A post-receive hook allows you to run commands after the Git repository has received commits. In this case, you can use it to change Git’s working directory from example.git to example.com, and check out a copy of the build into the example.com directory.

The location of the working directory can be set on a per-command basis using GIT_WORK_TREE, one of Git’s environment variables, or the --work-tree option.

cat > hooks/post-receive
#!/bin/sh
WEB_DIR=/path/to/example.com

# remove any untracked files and directories
git --work-tree=${WEB_DIR} clean -fd

# force checkout of the latest deploy
git --work-tree=${WEB_DIR} checkout --force

Make sure the file permissions on the hook are correct.

chmod +x hooks/post-receive

If you need to exclude some files from being cleaned out by Git (e.g., a .htpasswd file), you can do that using the --exclude option. This requires Git 1.7.3 or above to be installed on your server.

git --work-tree=${WEB_DIR} clean -fd --exclude=<pattern>

Repeat this step for the staging domain, if you want.

On your local machine

Now that the server configuration is complete, you want to deploy the build assets (not the source code) for the static site.

The build and deploy tasks

I’m using a Makefile, but use whatever you feel comfortable with. What follows is the basic workflow I wanted to automate.

Build the production version of the static site.
```
make build
```
Initialize a new Git repo in the build directory. I don’t want to try and merge the new build into previous deploys, especially for the staging domain.
```
git init ./build
```

Add the remote to use for the deploy.

cd ./build
git remote add origin ssh://user@hostname/~/example.git

Commit everything in the build repo.

cd ./build
git add -A
git commit -m "Release"

Force-replace the remote master branch, creating it if missing.
```
cd ./build
git push -f origin +master:refs/heads/master
```
Tag the checked-out commit SHA in the source repo, so I can see which SHA’s were last deployed.
```
git tag -f production
```

Using a Makefile:

BUILD_DIR := ./build
STAGING_REPO = ssh://user@hostname/~/staging.example.git
PROD_REPO = ssh://user@hostname/~/example.git

install:
    npm install

# Deploy tasks

staging: build git-staging deploy
    @ git tag -f staging
    @ echo "Staging deploy complete"

prod: build git-prod deploy
    @ git tag -f production
    @ echo "Production deploy complete"

# Build tasks

build: clean
    # whatever your build step is

# Sub-tasks

clean:
    @ rm -rf $(BUILD_DIR)

git-prod:
    @ cd $(BUILD_DIR) && 
    git init && 
    git remote add origin $(PROD_REPO)

git-staging:
    @ cd $(BUILD_DIR) && 
    git init && 
    git remote add origin $(STAGING_REPO)

deploy:
    @ cd $(BUILD_DIR) && 
    git add -A && 
    git commit -m "Release" && 
    git push -f origin +master:refs/heads/master

.PHONY: install build clean deploy git-prod git-staging prod staging

To deploy to staging:

make staging

To deploy to production:

make prod

Using Make, it’s a little bit more hairy than usual to force push to master, because the cd commands take place in a sub-process. You have to make sure subsequent commands are on the same line. For example, the deploy task would force push to your source code’s remote master branch if you failed to join the commands with && or ;!

I push my site’s source code to a private repository on BitBucket. One of the nice things about BitBucket is that it gives you the option to prevent deletions or history re-writes of branches.

If you have any suggested improvements, let me know on Twitter.

Full Article

LXer: 3 Best Free and Open Source Awk Static Site Generators

Kinsta Unveils High-Performance Platform for Free Static Site Hosting

Should you use Userbase for your next static site?

A textbook Userbase use case

Using Userbase

Is Userbase for you?

Should you use Userbase for your next static site?

A textbook Userbase use case

Using Userbase

Is Userbase for you?

Should you use Userbase for your next static site?

A textbook Userbase use case

Using Userbase

Is Userbase for you?

Should you use Userbase for your next static site?

A textbook Userbase use case

Using Userbase

Is Userbase for you?

A simple Git deployment strategy for static sites

Prerequisites

On the server

Set up password-less SSH access

Create the remote directories

Initialize the bare Git repository

Write a post-receive hook

On your local machine

The build and deploy tasks

LXer: 3 Best Free and Open Source Awk Static Site Generators

Kinsta Unveils High-Performance Platform for Free Static Site Hosting

Should you use Userbase for your next static site?

Should you use Userbase for your next static site?

Should you use Userbase for your next static site?

Should you use Userbase for your next static site?

A simple Git deployment strategy for static sites

Subscribe To Our Newsletter