# Self-Hosting #2: Git, Next, and failure ### Ingredients - The machine from [step 1](https://jinbyun.vercel.app/blogs/15) - A repo containing Next.js web application - A Github account ### Preparation ``` PS C:\Users\JinByun> dropbear Welcome to Termux! Community forum: https://termux.com/community Gitter chat: https://gitter.im/termux/termux IRC channel: #termux on libera.chat Working with packages: * Search packages: pkg search * Install a package: pkg install * Upgrade packages: pkg upgrade Subscribing to additional repositories: * Root: pkg install root-repo * X11: pkg install x11-repo Report issues at https://termux.com/issues ~ $ pkg install git ~ $ pkg install gh ``` Preparation is done. # Step 1: authenticating GitHub Now, with git and github installed, run `gh auth login`, it will guide you with some prompts.
This is what I have done. ``` ~ $ gh auth login ? Where do you use GitHub? GitHub.com ? What is your preferred protocol for Git operations on this host? HTTPS ? How would you like to authenticate GitHub CLI? Paste an authentication token Tip: you can generate a Personal Access Token here https://github.com/settings/tokens The minimum required scopes are 'repo', 'read:org', 'workflow'. ? Paste your authentication token: ********************** ``` Let's break down what each prompt is asking for. ### 1. Where do you use GitHub? Where else can you use Github? Is Github open-source? No, Github is not open source. However, Github has a product called **Github Enterprise**.
Github enterprise let the user(enterprise) self-host github, and that's what makes this question valid.
You do use GitHub, but not at https://github.com. So for a personal project just go with `GitHub.com` ### 2. What is your preferred protocol for Git operations? Here we have 2 choices. Let's start with SSH, since we went over it in last blog. #### SSH Similar to how we've set up the ssh server in the machine, we are now using the machine as ssh client and github as ssh server. It requires user to generate ssh key, add the key to your gh account, set up ssh-agent forwarding and more. #### HTTPS authenticate in browser (log in to browser) or tokens. That's it. #### Why SSH through all the complication? Well, in short, security and skill issue. With HTTPS, if a perpetrator has access to your machine, your github repos are very likely to be completely compromised. Also, the communication between client and server is hidden behind the black box. So if it fails, you won't know why. With SSH, you are given more power. You are the one that creates the passphrase and pass it on to GitHub. You can make your pc more secure by utilizing hardware keys. Without that key, perpetrators cannot try brute-forcing through the passphrase. Me, I just want to connect and get it over with, so I choose HTTPS ### 3. How would you like to authenticate gh? I normally go with browser authentication, since it's quick and easy.
But in this case, I have to use the token because I can't use the browser in termux (as it is). > Surprisingly, you can use GUI and install browser in termux. However, I don't think it will be feasible in my SM-P550.
*If you are interested, check [this link](https://wiki.termux.com/wiki/Graphical_Environment) on how and [this link to a video on example](https://youtu.be/H63LtxFyIuc?si=rD8QD5B5tK3pTks6&t=292)* To get the token, go to the [settings/token](https://github.com/settings/tokens) page and Generate new token. I used the classic token. Give it a memorable name, set the expiration date, and remember to give it **read:org, repo and workflow** permission. Once you generate the token, copy and paste it on to termux and you are authenticated! ## Step 2: clone, run and ... With access to the github repo, I cloned my web app (this page) ``` git clone https://thisrepo.git ``` and once done, I `cd`ed into the project. Before anything, I remembered that I needed my .env file, so I have copied my .env file from pc to termux. ``` // PC powershell type ./.env | ssh ipaddress -p 8022 "cat >> portfolio/.env" ``` And with the .env file, I tried ``` npm i ``` And hell started. ## step 3. Too Long record of failures ### First Err: node-gyp (source code builder for node) `npm i` threw `gyp: Undefined variable android_ndk_path in binding.gyp while trying to load binding.gyp` Apparently, this happens because termux is on android. The package node-gyp expects `android_ndk_path` to be set, but it isn't. A work around was found [here](https://github.com/termux/termux-packages/issues/20717#issuecomment-2196523557)
I followed the step to edit the `configure.js` file and the gyp ran clean! Problem solved! ### Second Err: Sentry (error logging service) compatibility Sentry CLI does not support Android. Who knew?!
Luckily, I don't use much of it. So It was easy to create a new branch called "termux" and removed sentry from the code.
With the new branch, now, ``` git pull git checkout termux npm i // was successful with the sentry removed npm run build > next build ▲ Next.js 14.2.16 - Environments: .env Creating an optimized production build ... Downloading swc package @next/swc-android-arm-eabi... ⨯ Failed to download swc package 14.2.16 ``` ### Third Err: SWC, or the lack of it SWC, or speedy web compiler, is what compiles next codes into production ready builds. However, The production of android version of SWC halted at version 13.2.4. So When I try to build or even dev the web app, the lack of valid swc just breaks the app. Below is a list of things I tried to fix it: - Install swc version 13.2.4 and wing it. - Try to use babel instead of swc for build (For some reason, Next doesn't let this happen) - Use next version 13 (results in segfault) - Use build from PC and try to run it in termux. I kinda expected next to fail in termux, but not in this way. I honestly expected it to just use up too much memory and kill the process, but failing at build, this is tough. On next blog, I will be trying to get a website actually running, and go over dynamic ip management (ddns). I'll probably go with Golang Backend. Stay tuned!