Post 9jVHxsha7DSjZ2K1dg by shpuld@shpposter.club
(DIR) More posts by shpuld@shpposter.club
(DIR) Post #9jVFIixTEnk9Yz07jk by waifu@pikachu.rocks
2019-06-04T12:24:31.793992Z
0 likes, 0 repeats
oh okay my prod.secret.exs is configured fine but the logo still doesnt show.okay
(DIR) Post #9jVFgsfAo5C0c1xfBw by rin@patch.cx
2019-06-04T12:28:54.490337Z
0 likes, 0 repeats
@waifu you are probably using deprecated configuration https://docs-develop.pleroma.social/config.html#fe
(DIR) Post #9jVFl3pPEmGsOljzbE by hj@shigusegubu.club
2019-06-04T12:29:40.321134Z
1 likes, 0 repeats
@rin @waifu if only we could keep using static config.json...
(DIR) Post #9jVFsrY6m41EdHN0pk by waifu@pikachu.rocks
2019-06-04T12:31:03.479303Z
0 likes, 0 repeats
@rin oh okay im not using either or something, i dont knowi just overwrote the pleroma logo file with pikachu file
(DIR) Post #9jVGYPc51toI9Z2YfA by rin@patch.cx
2019-06-04T12:38:35.122332Z
1 likes, 0 repeats
@waifu directly in priv/static or in instance/static?
(DIR) Post #9jVGlWjHsne5zLfIGm by waifu@pikachu.rocks
2019-06-04T12:40:57.154838Z
0 likes, 0 repeats
@rin i had something in that json HJ loves but I did "git checkout" on it because it said something about merge conflicts and it has been deprecated forever (or well, so I thought)in prod.secret.exs I have config :pleroma :fe but the logo and background rows clearly do not do their job
(DIR) Post #9jVGyS60QCl5NlSFO4 by rin@patch.cx
2019-06-04T12:43:17.268361Z
1 likes, 0 repeats
@waifu :fe is deprecated, you should use either https://docs-develop.pleroma.social/config.html#frontend_configurations or set managed_config to false and use json
(DIR) Post #9jVH3KEz3RNoT3ygJE by rin@patch.cx
2019-06-04T12:44:10.786496Z
0 likes, 0 repeats
@hj @waifu frontend_configurations is the last time we are changing it
(DIR) Post #9jVHC1jnDZI9ghXOfA by waifu@pikachu.rocks
2019-06-04T12:45:44.512645Z
0 likes, 0 repeats
@rin so it broke because it got deprecated and stuff?
(DIR) Post #9jVHalVIiBAwZyYU2y by rin@patch.cx
2019-06-04T12:50:13.035017Z
1 likes, 0 repeats
@waifu json is not deprecated, but :fe is. you can either- ensure that managed_config is set to false and modify the json fileor- open config.exs, copy the entire :frontend_configurations to your prod.secret.exs , modify it and ensure managed_config is set to true
(DIR) Post #9jVHfm1GDqw9crtNtw by waifu@pikachu.rocks
2019-06-04T12:51:06.864235Z
1 likes, 0 repeats
@rin WELL I RESETED/CHECKOUTED THE JSON BECAUSE I THOUGHT I WAS SUPPOSED TO USE :FE INSTEAD OF IT OKAY, that was long agoand now i gotta re-make it in :frontend_configurations for some reason
(DIR) Post #9jVHt8Wlqg7pCN0EyG by rin@patch.cx
2019-06-04T12:53:32.628297Z
1 likes, 0 repeats
@waifu sorry about that :c, we warned about the deprecation for like 3 months in startup messages but I guess nobody notices
(DIR) Post #9jVHun02rM9H0hU3lI by waifu@pikachu.rocks
2019-06-04T12:53:49.905938Z
0 likes, 0 repeats
@rin what are startup messages
(DIR) Post #9jVHxsha7DSjZ2K1dg by shpuld@shpposter.club
2019-06-04T12:54:23.051587Z
1 likes, 0 repeats
@rin @waifu I know I see no start up messages when I just launch the service
(DIR) Post #9jVICXaatUz8Qb2mRs by rin@patch.cx
2019-06-04T12:57:02.249622Z
1 likes, 0 repeats
@shpuld @waifu yeah, that's what I figured. ideally everyone will use releases starting 1.0 or read the changelogs so we will have a better way of notifying about breaking changes
(DIR) Post #9jVIL83jBSOVr0lYie by shpuld@shpposter.club
2019-06-04T12:58:36.283642Z
1 likes, 0 repeats
@rin @waifu yeah being able to know exactly what changes before updating is the way you want it, instead of just pulling and running
(DIR) Post #9jVIUsGikNfpmDUSpM by hj@shigusegubu.club
2019-06-04T13:00:20.768317Z
0 likes, 0 repeats
@rin @waifu yeah bun not everyone is following the changes closely
(DIR) Post #9jVIcUNRSXVJzkGUpk by Senkowo@letsalllovela.in
2019-06-04T13:00:25.135857Z
1 likes, 0 repeats
@rin considering you immediately get about 200 POSTS when you start up pleroma, you see startup messages for half a second at most, if you even check the logs.These messages should go in adminfe i guess, or more realistically just changelog once you get 1.0
(DIR) Post #9jVIcZa279Xy8FC7ea by rin@patch.cx
2019-06-04T13:01:45.333827Z
1 likes, 0 repeats
@Senkowo maybe we should set config :logger, level: :warn in prod by default
(DIR) Post #9jVIoHj0KG6EEIyXQm by calv@tanavega.xyz
2019-06-04T13:03:50.543544Z
0 likes, 0 repeats
@rin if I get some time I might see if I can implement announcements (maybe just for admins) in Pleroma, if it's wanted.
(DIR) Post #9jVItN5ZoGK4JWxVqa by flussence@kawen.space
2019-06-04T12:56:29.055488Z
0 likes, 0 repeats
@waifu @rin those things nobody reads, just like the duplicate key sql errors nobody reads
(DIR) Post #9jVItNJ30B68zJGGqO by waifu@kawen.space
2019-06-04T12:59:11.545435Z
0 likes, 0 repeats
@flussence @waifu @rin WHAT STARTUP MESSAGES AND WHERE IM SO FUCKING CONFUSED
(DIR) Post #9jVItNVSG31Tbn4BBQ by rin@patch.cx
2019-06-04T13:04:46.530400Z
0 likes, 0 repeats
@waifu @flussence @waifu I meant warning logs that pleroma prints on startup
(DIR) Post #9jVIyND4msWC8YqsZk by rin@patch.cx
2019-06-04T13:05:41.695845Z
0 likes, 0 repeats
@hj @waifu true, the default fe config should be merged with prod.secret.exs instead of being fully overriden
(DIR) Post #9jVJDhy3tOZkrO8ohk by waifu@kawen.space
2019-06-04T13:05:25.947639Z
0 likes, 0 repeats
@rin @flussence @waifu where does it print them because its not anywhere i could possible see them
(DIR) Post #9jVJDi9lBtvvRfc9wG by rin@patch.cx
2019-06-04T13:08:27.865173Z
0 likes, 0 repeats
@waifu @flussence @waifu depends on how you start pleroma, like shp said, most people do it via service so they never see them. you can view logs by executing journalctl -eu pleroma if you are on debian
(DIR) Post #9jVJWvAf1lKDJMCCC8 by waifu@kawen.space
2019-06-04T13:10:00.026810Z
1 likes, 0 repeats
@rin @flussence @waifu by the way, the brief example of the config in https://docs-develop.pleroma.social/config.html#frontend_configurations has wrong indentation of the },
(DIR) Post #9jVJWvS1zBDgBEK4Gm by rin@patch.cx
2019-06-04T13:11:55.073407Z
0 likes, 0 repeats
@waifu @flussence @waifu oh, you are right. I will fix it later
(DIR) Post #9jVK0Bab3zv0d6HWT2 by lain@kawen.space
2019-06-04T13:17:13.601593Z
0 likes, 0 repeats
@shpuld @rin @waifu that's the reason we also have changelogs and release notes.
(DIR) Post #9jVK9jpd7VhRR9rt5c by kaniini@pleroma.site
2019-06-04T13:18:56.487484Z
0 likes, 0 repeats
@lain @shpuld @rin @waifu the deprecation warning was removed when the fallback was removed.
(DIR) Post #9jVKHfDMAfQFQvkGjw by lain@kawen.space
2019-06-04T13:20:22.898621Z
0 likes, 0 repeats
@kaniini @rin @shpuld @waifu we could make it error out instead and get complaints about pleroma not starting instead of complaints about configuration not working
(DIR) Post #9jVKMN8qnBJqpVsnFw by kaniini@pleroma.site
2019-06-04T13:21:04.818260Z
0 likes, 0 repeats
@lain @rin @shpuld @waifu ...i was thinking we just put the deprecation warning back :)
(DIR) Post #9jVKRR1FnroeIskA0e by waifu@pikachu.rocks
2019-06-04T13:22:07.563846Z
0 likes, 0 repeats
@lain @kaniini @rin @shpuld I mean, I'm mostly just having a bad day, and I don't see warnings on stderr anyway, so like, this really is not the root of the problem
(DIR) Post #9jVKUTJ9kZqIGqZ70y by waifu@pikachu.rocks
2019-06-04T13:22:40.771183Z
0 likes, 0 repeats
@lain @kaniini @rin @shpuld I may think it's ridiculous that I deleted a json just to remake it without apostrophes, but like, in the end, there's not much that I can do
(DIR) Post #9jVKfbhStBGzU3FGhU by bhtooefr@snack.social
2019-06-04T13:22:42.558129Z
0 likes, 0 repeats
@kaniini @lain @rin @waifu @shpuld ...what about, when an admin user is logged in, actually showing the warnings in Pleroma FE somehow, too?
(DIR) Post #9jVKfbsoD0La3EYKNk by lain@kawen.space
2019-06-04T13:24:41.240519Z
0 likes, 0 repeats
@bhtooefr @kaniini @rin @shpuld @waifu we already have the info in the readme, the changelog and the deprecation warnings that are printed out on application startup. We can display messages like this in the admin frontend, though.
(DIR) Post #9jVKkdPVxOIcEjFL2O by hj@shigusegubu.club
2019-06-04T13:25:36.589463Z
0 likes, 0 repeats
@rin @waifu it is merged, but it's also in git IIRC and people got told that changing config.exs^W *.secret.exs is the way to go so people started doing that instead