jr/olomana
1
0
Fork 0
mirror of https://github.com/runyanjake/olomana.git synced 2025-10-05 05:37:29 -07:00
Code Issues Packages Projects Releases Wiki Activity

Compare commits

base: jr:da72f8fcc75eb91f3c980a3243e3b4046e368919
Branches Tags
jr:main
..
compare: jr:f74d3faf9849e9a4e70fd78b8f44c621ce25bdc9
Branches Tags
jr:main

No commits in common. "da72f8fcc75eb91f3c980a3243e3b4046e368919" and "f74d3faf9849e9a4e70fd78b8f44c621ce25bdc9" have entirely different histories.
da72f8fcc7 ... f74d3faf98

2 changed files with 6 additions and 33 deletions
Show Stats Expand all files Collapse all files

14
home/homeassistant/README.md
View File

@ -40,20 +40,6 @@ nmap -sn 192.168.1.xxx/24 (adjust for your local network)
1. Navigate to Settings > Automations & Scenes > Create Automation 1. Navigate to Settings > Automations & Scenes > Create Automation
2. Configure based on time, location, or other triggers. 2. Configure based on time, location, or other triggers.
### Issues
1. Bad Proxy
```
2025-03-15 09:13:37.969 ERROR (MainThread) [homeassistant.components.http.forwarded] Received X-Forwarded-For header from an untrusted proxy 172.18.0.2
```
Homeassistant container is receiving request from the docker proxy network, which it doesn't know about. Add the local proxy so that the container knows that it is ok.
```
http:
trusted_proxies:
...
- 172.18.0.2
```
If it doesnt take from the config manually edit it in the container.
## References ## References
https://www.home-assistant.io/integrations/wiz/ https://www.home-assistant.io/integrations/wiz/

25
software-development/gitea/README.md
View File

@ -4,25 +4,17 @@ Followed instructions on Gitea page: https://docs.gitea.com/next/installation/in
### Steps ### Steps
1. Create a new user to own the gitea folder. 1. Create a new user to own the gitea folder.
``` `sudo groupadd gitea && sudo useradd giteauser && sudo usermod -a -G gitea giteauser && chown -r gitea:giteauser .`
sudo groupadd gitea && sudo useradd giteauser && sudo usermod -a -G gitea giteauser && chown -r gitea:giteauser .
```
2. Run via Docker Compose 2. Run via Docker Compose
``` `docker-compose up -d`
docker-compose up -d
```
3. Test postgresql 3. Test postgresql
``` `docker exec -it gitea_db bash`
docker exec -it gitea_db bash `psql -h 127.0.0.1 -p 5432 -U olomana_readwrite -d gitea`
psql -h 127.0.0.1 -p 5432 -U olomana_readwrite -d gitea
```
4. Go to xxx.xxx.xx.xxx:3000 and fill out initial config. Everything should match up to default value. 4. Go to xxx.xxx.xx.xxx:3000 and fill out initial config. Everything should match up to default value.
Some things that were weird: Some things that were weird:
- could not use any port that wasnt default postgresql (5432) - could not use any port that wasnt default postgresql (5432)
- had to make sure to specify database container by the right name. Removed custom name and used just "database". - had to make sure to specify database container by the right name. Removed custom name and used just "databasei".
Note that the first admin is set via env vars, by generating the password hash. Alternatively create your users by setting the env var that controls signups. Additionally, you must provision the first admin user in the initial config.
5. Provision new users 5. Provision new users
You can do that from the "Site Administration" view from the first admin user. You can do that from the "Site Administration" view from the first admin user.
6. Configure SSH 6. Configure SSH
@ -47,10 +39,5 @@ entryPoints:
Settings > SSH/GPG Keys > Manage SSH Keys Settings > SSH/GPG Keys > Manage SSH Keys
Now should also be able to clone with SSH. Now should also be able to clone with SSH.
### Running
```
docker compose down && docker compose build && docker compose up -d && docker logs -f gitea
```
### References ### References
`https://docs.gitea.com/next/administration/config-cheat-sheet` `https://docs.gitea.com/next/administration/config-cheat-sheet`