Note by @jeder

Jeder

🔜 eth0 @jeder@miau.jeder.pl

2y

having a field day

1

1

1

1❤4⭐30😮1

6

13

0

39

Hayden @Hayden@wolfdo.gg

2y

@jeder @frost we need this here.

⭐1

1

0

1

Noble

@frost@wolfdo.gg

2y

@Hayden @jeder i would need to figure out how to install custom iceshrimp branch (and at that point i would want to figure out how to get the MOD player branch (and also i dont know how easy it'd be to migrate from biteshrimp to iceshrimp.net once thats done))

1

0

Jeder

🔜 eth0 @jeder@miau.jeder.pl

2y

@frost @Hayden it wouldn't really differ that much, I guess you'd have to revert a migration, anyway, I can uhhh, create a branch with this and mod tracker when i wake up
you are using git for updates right?

1

0

1

Noble

@frost@wolfdo.gg

2y

@jeder @Hayden yeah i always update by following these instructions for the tagged releases

1

0

Jeder

🔜 eth0 @jeder@miau.jeder.pl

2y

@frost @Hayden just creating a branch with mod tracker and bites rn and i have a question since i have that opened, do you also want a robots.txt that also makes your instance invisible to google crawlers etc btw? it's just another commit so nothing would change with later update procedure

⭐1

2

0

1

Jeder

🔜 eth0 @jeder@miau.jeder.pl

2y

@frost @Hayden anyway
you'll want to go to the repo folder
and do
git remote set-url origin https://iceshrimp.dev/jeder/iceshrimp.git which will set the repo you are pulling updates from to my repo
and then git fetch origin which will fetch stuff from it
and then git checkout bite-tracker, and then yarn commands from the docs

updating will be a matter of

git pull --rebase
yarn
yarn build && yarn migrate

👀1

2

1

0

1

Jeder

🔜 eth0 @jeder@miau.jeder.pl

2y

@frost @Hayden actually since i am a git rebase ~~ab~~user (this stuff doesn't work with normal git pull because it rewrites history) you'll want to use git pull --rebase instead

📝1

0

1