HebaruSan[m] has quit [Quit: Idle timeout reached: 10800s]
DasSkelett[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has joined #spacedock
<VITAS[m]>
everything is fine to update they said. itl be good they said.... :/
<VITAS[m]>
is that master conflict thing solved now?
HebaruSan[m] has joined #spacedock
<HebaruSan[m]>
GitHub's master branch has not changed. I can't check what prod looks like.
<VITAS[m]>
darklight would know
<VITAS[m]>
ill call him over when hes awake
<VITAS[m]>
Darklight
<VITAS[m]>
Because you had commits on master and beta/alpha are not children of master, prod is on the beta branch
<VITAS[m]>
Specifically, prod is on e91894465c3a2885531355b9c813493ad93eaca4
<VITAS[m]>
so we have to throw away what is on master and use that on it
<VITAS[m]>
because master has no relevance anymore
<VITAS[m]>
are you able to do that HebaruSan ?
<VITAS[m]>
Darklight
<VITAS[m]>
Personally I would like prod to track master, but there is dangling commits that need to be looked at
<VITAS[m]>
Currently prod is on beta that night we updated it, that commit ^
<RockyTV>
also
<RockyTV>
04:50:51 <RockyTV> we can checkout master to old and reset master to beta
<RockyTV>
in that case, the specific commit on prod
<VITAS[m]>
i personaly dont care what happens to old master code because im pretty sure its not relevant anymore if they are older commits.
<VITAS[m]>
DasSkelett: did a lot of work since then
<VITAS[m]>
but yes we can put it somewhere for documentary reasons
<HebaruSan[m]>
That doesn't make sense to me. alpha and beta were branched specifically from master. Where did these extra commits come from?
Darklight[m] has joined #spacedock
<Darklight[m]>
Thought I might jump back in
<Darklight[m]>
<span class="d-mention d-user">HebaruSan</span> I've set the old master that prod had to old-master as it has dangling commits, and forced reset master to the deployed version we did that night
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
Shuudoushi has quit [Ping timeout: 378 seconds]
HebaruSan[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has joined #spacedock
<VITAS[m]>
hmm prod did differ from master in the past
<VITAS[m]>
because i manualy patched stuff on it when moving servers
<VITAS[m]>
maybe those are it
<VITAS[m]>
but i think it doesnt matter
<VITAS[m]>
prod is running fine and we need consistency
<VITAS[m]>
i take that over some code
<VITAS[m]>
especialy with the amount of work done to alpha at since the last prod update
<VITAS[m]>
also may may i add: Im so happy that theres progress and activity :)
<Darklight[m]>
You have about 10 dangling commits on old-master
<Darklight[m]>
Oh I thought there was some merge commits that pulled in some bugfixes, related to markdown, I didn't actually check that it was in master, nevermind ^_^
<DasSkelett[m]>
Yeah it looks like the commits themselves are in master, just not the merge commits. A partial cherry-pick attempt I guess.
<VITAS[m]>
so even if it says 2019 it might be years old stuff
<Darklight[m]>
There is some vitas commits that are in the timeline
<VITAS[m]>
i dont see any reason to dig trough them
<VITAS[m]>
prod is working like it should
<VITAS[m]>
you DasSkelett added new stuff
<DasSkelett[m]>
I'm gonna restore the funding button and merge it to alpha
<VITAS[m]>
i remember experimenting with a patron progress bar years ago too
godarklight[m] has joined #spacedock
<godarklight[m]>
Quaternion is prettier than pidgin but it has nothing on discord
<VITAS[m]>
huh?
<VITAS[m]>
riot
<VITAS[m]>
is where its at
<godarklight[m]>
Yeah I just installed it, this is way better
<VITAS[m]>
and cross platform
<godarklight[m]>
WHERE IS DARK THEME
<VITAS[m]>
options
<VITAS[m]>
mine is in dark
<VITAS[m]>
settings general
<VITAS[m]>
half way down: theme
<godarklight[m]>
Got it
<godarklight[m]>
I was looking at room settings
<Darklight[m]>
What room is the DMP one?
<VITAS[m]>
#dmp:52k.de i presume
<VITAS[m]>
its #irc_#dmp:52k.de
<VITAS[m]>
here
Shuudoushi has joined #spacedock
<DasSkelett[m]>
<span class="d-mention d-user">HebaruSan</span> do you want to have another look at the admin area PR, or should I go ahead and merge it?
godarklight[m] has quit [Quit: Client limit exceeded: 6]
HebaruSan[m] has joined #spacedock
<HebaruSan[m]>
Go for it
<DasSkelett[m]>
Should I make you admin on alpha, so you can try it out? Having the pgAdmin opened right now.
<HebaruSan[m]>
Sure, why not
<DasSkelett[m]>
Well, throwing an internal server error now. Oups...
<DasSkelett[m]>
Ah I see why... Hang on a minute, crafting a fix.
<DasSkelett[m]>
Actually, I think that's not my fault, it's just the server which didn't restart and just reloaded the templates.
<DasSkelett[m]>
Yep, manually restarting works. We need to have a look at the restart webhook, they don't really work currently.
<HebaruSan[m]>
The blog UI could use some attention, by default it shows one line of one long post and you have to click to expand, with links that aren't clickable
<HebaruSan[m]>
(viewing not editing)
<HebaruSan[m]>
Might make sense to announce the existence of the alpha and beta servers
<DasSkelett[m]>
> with links that aren't clickable
<DasSkelett[m]>
You mean the "Read more, leave a comment, etc"? I can click that.
<VITAS[m]>
only advertise beta to the public and alpha to people who can code
<VITAS[m]>
e.g. mod devs
<VITAS[m]>
"normal" users cant see past obvious missing things
<VITAS[m]>
that could exist in alpha stages
<DasSkelett[m]>
Maybe we could use the blog posts as maintenance warning, instead of implementing a new mechanism 🤔
<VITAS[m]>
good idea
<VITAS[m]>
i myself see the blog more as cms anyways
<HebaruSan[m]>
Maybe we announce beta on the prod blog, then announce alpha on the beta blog
<HebaruSan[m]>
I would find that amusing
<VITAS[m]>
if you wish
<VITAS[m]>
i was thinking of announcing alpha stuff on github
<VITAS[m]>
and initialy on the forums/dev hole
<VITAS[m]>
beta in the main spacedock thread and on prod
<VITAS[m]>
we could also have a feedback/issue button right there on alpha and beta
Darklight[m] has quit [Quit: Client limit exceeded: 6]
Chaos_02[m] has joined #spacedock
<Chaos_02[m]>
evening, I cant reach spacedock for some reason on private network
<DasSkelett[m]>
(We started the investigation over in the DMP channel)
<Chaos_02[m]>
also not on mobile data from phone
<DasSkelett[m]>
So only if you try accessing it over your WiFi / LAN?
<Chaos_02[m]>
if I click on the page from google just nothing happens, when opening any other ways the page just stays black with no error or browser console output
<Chaos_02[m]>
> So only if you try accessing it over your WiFi / LAN?
<Chaos_02[m]>
no on all available connections
<DasSkelett[m]>
Weird... Do you know how to open the Windows command prompt/console?
<Chaos_02[m]>
I dont think it is blocked by ISP because I'm in germany but atm I am suspecting it?
<Chaos_02[m]>
yes, the netstat cmd?
<Chaos_02[m]>
no traceroute, right?
<Chaos_02[m]>
dont recall the right one anymore
<DasSkelett[m]>
Try `nslookup spacedock.info` first, to see if it even resolves properly.
<DasSkelett[m]>
I think the browser in your screenshot was Chrome, do you have another one installed you can try?
<Chaos_02[m]>
~~spacedocks~~
<DasSkelett[m]>
*edit:* ~~Yeah that's expacted to happen.
<Chaos_02[m]>
well, edge but it also doesnt work on mobile?
<DasSkelett[m]>
I think the browser in your screenshot was Chrome, do you have another one installed you can try?~~ -> Yeah that's expected to happen.
<DasSkelett[m]>
I think the browser in your screenshot was Chrome, do you have another one installed you can try?
<Chaos_02[m]>
😳
<Chaos_02[m]>
it works on edge wtf
<Chaos_02[m]>
google!?
<Chaos_02[m]>
well thanks for the help I will investigate further
<DasSkelett[m]>
Hmm, then I suspect it's some browser addon making problems (because I doubt it's failing for every Chrome user, we'd have some more reports then 😄 ).
<DasSkelett[m]>
Try disabling all addons.
<Chaos_02[m]>
I have chrome on mobile yes but it doesnt have addons so I dont think its an addon but rather the fact that I am using the beta version (chrome canary)
<Chaos_02[m]>
never seen it fail on a single site when it does
<DasSkelett[m]>
Are you also using Chrome Canary on your desktop?
<Chaos_02[m]>
yes
<DasSkelett[m]>
Looks like they broke something huge then. Hope they don't release it into Chrome Stable soon 😬
<Chaos_02[m]>
they usually notice it first but this is literally the only page thats making trouble..? 😂 🤔
<Chaos_02[m]>
alright thx
<Chaos_02[m]>
have a good one then
<DasSkelett[m]>
I'm installing Chrome Canary now too, let's see if it's also broken for me.
<DasSkelett[m]>
Hmm, works fine in the mobile app.
<DasSkelett[m]>
Are you using any firewall software or antivirus on your phone and your PC <span class="d-mention d-user">@_discord_265895468876169226:t2bot.io</span>?
<VITAS[m]>
google is broken
<VITAS[m]>
who would trust a company who cant spell gogol correctly?
SA56[m] has joined #spacedock
<SA56[m]>
Hi guys
<DasSkelett[m]>
I think we can merge the SpaceDock and DMP channels now. The userbase is now pretty much the same 😄
<SA56[m]>
Wait, is one of you managing SpaceDock?
<DasSkelett[m]>
VITAS is the guy who pays for and runs everything, HebaruSan, Rocky and me are trying to keep it running.
<SA56[m]>
So VITAS has two domains? :P
<DasSkelett[m]>
As in website domain? Not only two...
<SA56[m]>
I guess they're all pointing to the same machine
<DasSkelett[m]>
Yes pretty much
<DasSkelett[m]>
Everything behind one giant reverse proxy / traffic server.
<SA56[m]>
sounds pretty expensive
<DasSkelett[m]>
I don't have any numbers, but I'm sure it's not cheap.
<HebaruSan[m]>
There's a Patreon link on the SD blog if you want to chip in 🙂