I did a fresh install of Superdesk (sdsite branch) on http://desk.unimedia.info. I did not make any config changes, but I already have some errors on main.log. Is it a warning or a config error? Could you please tell me if I can move forward with configuration?

You can also set PUBLISHER_API_SUBDOMAIN env var set to "beta" and PUBLISHER_API_DOMAIN env var set to "unimedia.info" while deploying/installing Superdesk so it will automatically set proper env vars for you without a need to change the above config.

On the Publisher side (assuming you already have it installed):

1. Run command php app/console swp:organization:create Unimedia

This command will create a a proper organization if you didn't create it.

P.S.: As for the Superdesk configuration - it all went well after I made the config (and rebuild - I never did rebuild after reconfiguring) for the client side. Although in the console I get some cors error:

Looks like the theme name is not set for current tenant (probably a bug let me know pls). Check in swp_tenant table if the tenant hasswp/default-theme (this name is from theme.json) set in theme_name column.

You were right: there was no value for the theme_name for the tenant in the swp_tenant table. I did the change on the table (added: swp/default-theme). Now it loads, but i guess there is something wrong with the assets (style.css and all.js).

Rafał, I had a productive morning :) The issue with auth endpoint was because there was not a role set for the user (my user, might be a bug). I created a role and assigned it to me and now everything is fine.

I managed to solve CORS problem with the help of Nginx configuration, adding the needed header there.

Now the saga is to bring the menu I created in the Superdesk to the default theme. I browsed through the templating documentation and sadly I did not found much info.

Your help is really priceless. Thank you.

UPDATE

I copied and replaced the menu invocation tag from the theme-dailyNews and placed it in the base.html.twig -> Now I see the menu.

I still did not manage to bypass the auth issues. On the SWP site, i get this error in the console:

I installed Superdesk together with Publisher, but when I'm going to test Publish an article the Publishing Menu DOES NOT GIVE ME THE OPTION TO PUBLISH IN MORE THAN ONE SITE, as shown in the following figure01 ...

I ask, what should I do to have access to the Publication menu like figure02 attached ...

Offtopic: Anyway things are very confusing. There is no clear info anywhere on how to install no docker Superdesk to work along with SWP.

Same confusion persists when adding two (or more) `ouptut` sites (SWPs), because, for example, in instructions, you hardcode Publisher's settings in superdesk.config.js. That is for ONE Publisher. I added a seccond site, and it appears in Dashboard, but not always. Sometimes it is displayd only the seccond SWP i added, but after a refresh - the firtst SWP ("hardcoded" in config) - also appears.

There is still that info that "Custom fields will be added to SD Site", but as i understand it was not done, and "it will be done in a future release".

I searched for a way to feed the Superdesk through Content API (or through ANY API) - same "success" on finding clear info in Sourcefabric documentation.

I understand that your business model forces you to play and be adequate in support and documentation with big players and publishers - but if you (the ones that created this beautiful piece of software) don't provide such information and care, who should?

I understand that Superdesk and SWP are not "next->netx->next>installed" type of a product, but... c'mon.

P.S.: In this context, articles on your blog like "Why Open Source is Good News for the News Media" and the ones about how many big publishers are joining Superdesk adventure smells like trolling.

Pawel, thanks, it was an... old opinion, meanwhile, i concentrated on Superdesk only, writing my own solution for the news site (which uses Superdesk as a "backend", of course). With the help of Petr Jasek we will launch the beta site on Monday (if it all goes well). But that's one site for one publisher. I still got to make a second site for this publisher, and another one for my own company, so, thanks for the update, as I will give it a try as soon as possible.