Windows sections will be added later. For now check out these links to set up:
- Install Homebrew by running command:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)". (This will ask for you password and confirmation of download) - Check that homebrew is up to date and healty by running:
brew updatethenbrew doctor
- Install Postgres by running:
brew install postgresql - Start Postgres service by running:
brew services start postgresql - If you get error: "Error: role 'postgres' does not exist", run command:
/usr/local/opt/postgres/bin/createuser -s postgres
Remember to run npm run build and npm run develop after doing these steps.
PS: The step “Downloading Command Line Tools for Xcode” can take very long. My best suggestion for that is checking out this discussion: Homebrew/discussions#131
And especially this comment:
Apple's XCode command-line installer is...quite uncommunicative. You have at least two choices: 1. Wait for as long as it takes...or the installer errors out. 2. Go to https://developer.apple.com/download/more/ (you'll need to sign up for an Apple developer account if you don't have one), then download and install the latest Command Line Tools package that your OS supports.
After setting up strapi, you need to import the database. This is how you do that.
- First, add the database file to the native layer in your repo. It should be named something like “backup-remote-….-.pgsql”
- In your terminal, go into postgres:
psql template0 - Check roles:
\du- You will most likely see that you are a "superuser" in some databases, some not. This gives special admin rights to the database, which you will need
- Create database for this project, call it "acc-v4":
CREATE DATABASE "acc-v4". - Make yourself a superuser:
alter user [username] with superuser. - Add login permission:
alter role [username] with login - Exit postgres:
\q - Import the database:
pg_restore -U [username] -d acc-v4 -1 [name-of-file] - Run
yarn buildand thenyarn develop. You should now be set up. Go to http://localhost:1337/admin/ (Or whatever localhost it is running on) and check!
- To import the database correctly, it needs to be totally empty when you do it. When you are not familiar with PostgreSQL it is easy to type wrong, make small mistakes etc., which can lead to the database not being ready to import when you try. This can be easily solved by deleting the database
DROP DATABASE [name-of-database]and creating a new oneCREATE DATABASE [name-of-database]. This will give you a clean slate to try importing again. - Always remember
;at the end of your lines, commands in PostgreSQL wont run without them. If you forget, just type;in the next line and pressENTER. - Backslash is achieved with
SHIFT+OPTION+7on a Mac.
Most of the steps here are taken directly from this website: https://www.moncefbelyamani.com/how-to-install-postgresql-on-a-mac-with-homebrew-and-lunchy/. There is more to learn there.
HomeBrew is a package manager that takes care of everything NPM or Yarn doesn´t. Read more about it on https://brew.sh/
It will ask for your password and to confirm the download.
Beware that the step “Downloading Command Line Tools for Xcode” can take very long. My best suggestion for that is checking out this discussion:
And especially this comment:
Apple's XCode command-line installer is...quite uncommunicative. You have at least two choices: 1. Wait for as long as it takes...or the installer errors out. 2. Go to https://developer.apple.com/download/more/ (you'll need to sign up for an Apple developer account if you don't have one), then download and install the latest Command Line Tools package that your OS supports.
Don´t worry, it takes some time, but will complete in the end.
After all this, you might get the error: “error: role "postgres" does not exist”
To solve that, simply run this in the command line:
/usr/local/opt/postgres/bin/createuser -s postgres
Then, run "yarn build” and "yarn develop” again and you should be good!
When you work on this project, you will du that on your own fork. You will make branches for each added feature, push changes and then merge the branches when the feature are reviewed by others. Here is a breakdown of your workflow:
- Set upstream repo. Olivers repo is our "source of truth":
git remote add [email protected]:oriooctopus/acc-v4.git - Pull master - make sure you´re up to date:
git pull - Make a branch for the change you´re about to make:
git checkout -b [name-of-branch] - Make the changes/Write the code
- Add changes with
git add [name-of-file - Commit changes with
git commit -m "[notes about changes]" - Push changes:
git push origin HEAD - Go to github and make a pull request for your changes.
In general there is some thing you need to learn about working with git. Don´t be afraid to ask. You should also go through this tutorial on git branching, it is very helpful: https://learngitbranching.js.org/
- Git Lens is a very helpful VSCode extension: Go install it. (Add picture etc.)
- When you have made your branch, you can check your branches by entering this command:
git branch. It will also tell you which branch you are on. - When you have made a pull request on a branch and make more changes. Don´t make another pull request, it will update when you push the new changes.
- When you type git rebase -I HEAD~[num] you, for some fucking unknown reason, enter this vim fuckery. Without a fucking course you will also be stuck there and god forbid the changes you want to make will actually be made. So, here is a little guide for how to deal with this godforsaken dickcheese of a feature.
- :q - no changes were made
- :q! - trash all changes
- :wq - save the changes and quit