Skip to content

Commit

Permalink
chore: use .env instead of Makefile.variable (#6)
Browse files Browse the repository at this point in the history
## Summary

Renaming all occurences of `Makefile.variable` with `.env` since that is
the more standard approach.
  • Loading branch information
navneel99 committed Jul 30, 2024
1 parent ee856ec commit ce8016c
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 6 deletions.
File renamed without changes.
2 changes: 1 addition & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -9,4 +9,4 @@

build.tar.gz
nohup.out
Makefile.variable
.env
6 changes: 3 additions & 3 deletions Makefile
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
include Makefile.variable
include .env

# export values in Makefile.variable to be used in the shell scripts
export $(shell sed 's/=.*//' Makefile.variable)
# export values in .env to be used in the shell scripts
export $(shell sed 's/=.*//' .env)

default:
$(MAKE) build
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,8 @@ This GitHub repository provides a template with example code to implement an Air

2\. Open the project in your IDE and set up project environment variables, by following these steps:

- Rename `Makefile.variable.example` to `Makefile.variable`.
- In `Makefile.variable` set the slug of your organization, and your email.
- Rename `.env.example` to `.env`.
- In `.env` set the slug of your organization, and your email.

4\. Build the Snap-in using the following command:

Expand Down

0 comments on commit ce8016c

Please sign in to comment.