Hi Alessandro,

That's great to hear.

Looking through my old emails, I see you wanted to disable project creation
for ordinary users. If you still want that, you should now be able to
configure that, by editing the 'user' role in Administration/Manage Roles
and removing the 'project-creator' role.

Regards,

Sean.

On 15 February 2018 at 00:39, Portosa Alessandro <alessandro.port...@eng.it>
wrote:

> Dear Sean,
>
> I have been able to update my instance with the latest Zanata release.
> Everything went quite smooth. I followed the release notes and the
> installation guide.
>
>
> At this very moment, everything seems to be well configured!
>
>
> Thanks you very much. You did a great job with this latest versions!
>
>
> Cheers,
>
> Alessandro
>
>
> ------------------------------
> *Da:* Sean Flanigan <sflan...@redhat.com>
> *Inviato:* mercoledì 14 febbraio 2018 02:03:13
>
> *A:* Portosa Alessandro
> *Cc:* zanata-users@redhat.com
> *Oggetto:* Re: [zanata-users] Error 503 while getting Zanata resources
> from Red Hat server
>
> Hi Alessandro,
>
> Zanata is designed to update its database schema automatically at startup
> if required (using Liquibase), but there have been some changes in the
> config files (eg EAP's/WildFly's standalone-full.xml). In fact, moving from
> Zanata 3.x to 4.x, you will need to upgrade JBoss EAP or WildFly too (which
> use a whole new standalone-full.xml baseline).
>
> Zanata's release notes are here: http://docs.zanata.org/
> en/release/release-notes/ You can skim past all the bug numbers, but the
> text in between includes actions which the system administrator must take
> for each upgrade.
>
> And the installation guide (may be up to date): http://docs.zanata.org/
> en/release/user-guide/system-admin/configuration/installation/
>
>
> You basically need to add your system properties (adjusted as per the
> release notes), configure a new Infinispan cache and a JMS queue (as per
> release notes) and configure SMTP.
>
> This JBoss CLI file shows how we customise standalone-full.xml for some of
> our tests: https://github.com/zanata/zanata-platform/blob/
> 2e2d1ea124255b6f4edaf979e5f28731dbd56e5f/server/docker/conf/
> zanata-config.cli - although you will need to put in your own values, eg
> file system paths and database config, plus you don't need all the logging
> config and you probably don't need so many authentication systems.
>
> I would *strongly* recommend testing the upgrade (with a copy of your
> production data) before upgrading your production machine. Especially in
> view of the app server upgrade.
>
> Regards,
>
>
> Sean.
>
>
>
> On 12 February 2018 at 19:24, Portosa Alessandro <
> alessandro.port...@eng.it> wrote:
>
> Hi Sean,
>
> thanks for your answer. Is there any guide regarding how to upgrade from
> Zanata 3.5.1 or so?
>
> Does it uses the same database schema, and things like that?
>
>
> Our instance is in production, and I would prefer to do not brake
> anything...
>
>
> If you could provide link to resources, I will appreciate that.
>
>
> Regards,
>
> ------------------------------
> *Da:* Sean Flanigan <sflan...@redhat.com>
> *Inviato:* lunedì 12 febbraio 2018 02:26:24
> *A:* Portosa Alessandro
> *Cc:* zanata-users@redhat.com
> *Oggetto:* Re: [zanata-users] Error 503 while getting Zanata resources
> from Red Hat server
>
> Hi Alessandro,
>
> The host assets-zanata.rhcloud.com was running on OpenShift Online v2,
> which was recently decommissioned.  I thought we had sent a warning a few
> months ago, but apparently we forgot, sorry.
>
> Newer versions of Zanata package these assets into the application to
> avoid the problem you have encountered. I suspect Zanata 3.7 would work,
> with a broken logo or two, but it's very old so we haven't tried it. See
> https://zanata.atlassian.net/browse/ZNTA-1933
>
> Zanata 3.5.1 is over three years old now. I would recommend upgrading
> Zanata to the latest version (4.4.3) to take advantage of recent bug fixes
> and enhancements.
>
> Regards
>
> Sean.
>
>
> On 11 February 2018 at 23:47, Portosa Alessandro <
> alessandro.port...@eng.it> wrote:
>
> Hi all,
>
> we are facing a technical issue since a couple of week.
>
> It seems that something has changed in redhat server and our own Zanata
> instance (v3.5.1) is not able to get the required resources from your
> servers. Please see screenshot below:
>
>
>
>
>
> Is there anyone facing the same issue? What's wrong the host
> assets-zanata.rhcloud.com?
>
>
> Regards,
>
> Alessandro
>
>
> _______________________________________________
> zanata-users mailing list
> zanata-users@redhat.com
> https://www.redhat.com/mailman/listinfo/zanata-users
>
>
>
>
> --
> Sean Flanigan
>
> Principal Software Engineer
> Globalisation Tooling, Customer Platform
> Red Hat
>
>
>
>
> --
> Sean Flanigan
>
> Principal Software Engineer
> Globalisation Tooling, Customer Platform
> Red Hat
>



-- 
Sean Flanigan

Principal Software Engineer
Globalisation Tooling, Customer Platform
Red Hat
_______________________________________________
zanata-users mailing list
zanata-users@redhat.com
https://www.redhat.com/mailman/listinfo/zanata-users

Reply via email to