You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,11 +34,19 @@ You can fill out most of your information in /src/configs.js to autofill most of
34
34
35
35
### Projects
36
36
37
+
1) If you're manually pushing the build files to your hosting service like AWS S3 or Firebase -
38
+
37
39
After running npm build, create a 'projects' folder in the build folder, then create another folder for the project, and drop other React build files in there or any static files. Then, link the file path to the project from the <a> tag used in the projects section.
38
40
39
41
ex. build/projects/calculator/index.html
40
42
41
-
For deploying react projects inside the portfolio, there's a special configuration needed. Before building the project app, add below line to the package.json file.
43
+
2) If you're using automated deploy process such as Netlify -
44
+
45
+
Same idea as above, but you have to manually copy over the static files into the build folder after the build process completes. In your Netlify build command, you can use the `cp -r` command - ex. `yarn build && cp -r ./calculator ./build && cp -r ./sgt ./build`. This will copy over your project files after the build process completes.
46
+
47
+
NOTE - FOR BOTH 1) and 2)
48
+
49
+
For deploying react projects inside the portfolio, there's a special configuration needed. Before building the project app, add below line to your project's `package.json`.
@@ -48,9 +56,7 @@ Refer to [this](https://facebook.github.io/create-react-app/docs/deployment#buil
48
56
49
57
### Resume
50
58
51
-
After running npm build, drop resume.pdf in the folder before deploying.
52
-
53
-
If you want to structure the folders differently, feel free to change up the <a> tags in the template respectively.
59
+
Place your `resume.pdf` file somewhere in the repo, (ex. `src/`) and import the file as a variable and set it as the `href` for the resume buttons. Refer to [this](https://stackoverflow.com/a/49882656/8711377) post for exactly what it looks like.
54
60
55
61
### Contact/Email
56
62
@@ -70,7 +76,7 @@ If you want to structure the folders differently, feel free to change up the <a>
70
76
71
77
### Deploying
72
78
73
-
I like to use Firebase for my deployments, because I usually separate my frontend and backend. But you're free to deploy it anywhere you'd like. Just make sure to drop in your resume and projects before deploying.
79
+
~I like to use Firebase for my deployments, because I usually separate my frontend and backend. But you're free to deploy it anywhere you'd like. Just make sure to drop in your resume and projects before deploying.~ Netlify makes the whole process a lot easier. Make sure to refer to 2) above to deploy your projects properly.
0 commit comments