There was a need to disable account registration on the login page.
After small search i found an issue on github and when this option has been added:
https://github.com/kiwitcms/Kiwi/issues/2500
I found required parameter at /tcms/settings/common.py and official documentation show me to change value of REGISTRATION_ENABLED to False:
https://kiwitcms.readthedocs.io/en/stable/configuration.html
I changed value and restart docker container from directory with it:
docker-compose restart
But account registration field still appear. Clearly, further action is required. But I can't find the answer in the official documentation and I don't have enough experience with docker. Thanks.
When I carefully read the documentation again, i'm realized that any customization requires remake the docker image:
https://kiwitcms.readthedocs.io/en/latest/installing_docker.html#customized-docker-image
I updated repository under kiwi directory:
git fetch
git checkout v11.7 //latest kiwi release at this moment
had made necessary changes at tcms/settings/common.py
built new docker image:
make docker-image
and started services:
docker-compose up -d
Related
I am trying to deploy a react app, but specifically on user page on github pages. I can see a LOT of resources for deploying to project page, but nothing yet for user page. Please help!!!
I have tried switching the gh-pages line in the package.json file to include master, but even then I will have to update the gh-pages branch, it doesn't deploy directly from master. I want to be able to deploy directly from master.
gitname/react-gh-pages is one good example, and applies to a user site, where GitHub requires that the repository's name have the following format: {username}.github.io (e.g. gitname.github.io).
But it uses the gh-pages branch as publication source, not master (which no longer exists anyway, since it was renamed to main since Oct. 2020)
The OP cheese-berry references in the comments the post "How do I deploy a simple React app as a "user page" to Github Pages?"
cheese-berry adds:
For anyone else with the same question, you need to basically:
pay attention to your repo name,
install the gh-pages package,
modify your package.json file, and
change your source of deployment on GitHub (Repo -> Settings -> Pages -> Build & Deployment).
Apologies, I am still a bit confused by git, although I am trying to teach myself more and improve.
I recently successfully deployed a React website to GitHub pages, following the often recommended steps of installing gh-pages to the project, adding a homepage property to the package.json file, adding scripts to the scripts properties on the package.json file, running 'npm run deploy' and so on. It worked fine, and now a build of the project has been added to my repository (here), and I can view the actual project online (here).
However, the issue I have is this: most guides on deploying a react app also mention the following steps:
in the terminal type:
git add .
git commit -m "commit"
git push origin master
These final steps are often listed as optional. Everything worked fine without me doing these steps: my code was added to the repository, and my website is deployed online, so what do these steps do exactly? Why are they considered optional? What is best practice?
These commands are not optional to me - when using only the command-line Git client, these commands accomplish the interaction of pushing the code (that, after you edit it, only exists locally on your own PC) to the Git repository server.
Everything worked fine without me doing these steps: my code was added to the repository, and my website is deployed online
I can see the following possibilities:
You are using another Git client and the push was done there;
You are using a Git tool (e.g. editing purely on the GitHub website), where the push happened without you being aware of it;
You did the terminal commands, without being aware of them;
A common resource to learn more about Git would be the Git book on the official Git SCM website: https://git-scm.com/book/en/v2
I am using Google Cloud to deploy my application. I have followed the steps in the documentation for deploying. I deployed early on in my project and it was successful. I then decided to change some files and update some features in my app. For this i followed the documentation for updating a deployment. This update was successful. It had me create the deployment in my Deployment Manager and run the gcloud commands to commence update. When I redeployed with gcloud app deploy, it was successful.
I have since added a couple more lines of code and features in my application. I followed the same documentation for updating a deployment as I had the first time I made an update and it is no longer working for me.
Does anybody have any idea what would be the problem? Again, I was able to successfully deploy, and even update that deployment once by following Google Cloud docs. Now I am having no luck.
Have you been changing the version number? Go to:
https://console.cloud.google.com/appengine/versions?project=< your project name >&serviceId=default
And make sure the version you want is active. Also, you can try:
http://<VERSION>-dot-<SERVICE>-dot-<PROJECT_ID>.<REGION_ID>.r.appspot.com
Example:
https://20200813-dot-myapp.uc.r.appspot.com
if the version number was 20200813 and your appname is myapp and the region is uc
I would like not only to install the engine, but also to put on your local machine the documentation that you have on the official website. For the reason that I do not have permanent Internet access.
https://reactjs.org/ - > https://localhost:3000/
Is it possible to do this?
The reactjs.org website is also hosted on Github in this repository: https://github.com/reactjs/reactjs.org
Clone that to your computer and follow the Getting started guide guide on the readme page. After running yarn and yarn dev in the project directory, the site should be visible on http://localhost:8000
You can use DevDocs Offline. They have a wide range of documentation available.
Search for React and install. You will be able to access
I've been trying to install and setup the ASK CLI for a days now. I've followed the setup instructions and was able to install it. Whenever I try to run the ask init command and choose the "No. Skip AWS credentials association step.", a browser opens up and asks me to login to my developer account. I enter my credentials and just get redirected to a page that says unable to connect (Here's the link: http://127.0.0.1:9090/cb?code=ANjcJMpKRGqoqrSbiHdX&scope=alexa%3A%3Aask%3Askills%3Areadwrite+alexa%3A%3Aask%3Amodels%3Areadwrite+alexa%3A%3Aask%3Askills%3Atest+alexa%3A%3Aask%3Acatalogs%3Aread+alexa%3A%3Aask%3Acatalogs%3Areadwrite&state=Ask-SkillModel-ReadWrite).
I also tried using the ask init --no-browser command. I paste the generated url to a browser (I've tried Google Chrome, IE, Edge and Firefox and so far Firefox and IE works well). It gives me an authentication code but when I go back to the terminal, it's just frozen. I can't paste anything to it. I always get stuck at this point.
The reason I'm choosing "No. Skip AWS credentials association step." is because my skill endpoint is hosted as a web service in Azure and not using AWS Lambda. Am I missing anything? There were no errors in the installation process. I installed nodejs and git correctly. When I do ask --version in the terminal, the result is 1.4.7.
Does the ASK CLI not allow the skipping of the AWS profile setup?
A few details to make it clearer:
OS: Windows 10
Node JS: v10.13.0
NPM: 6.4.1
Git: git version 2.19.1.windows.1
ASK: 1.4.7
(I also found someone who experienced the same problem: ASK CLI INIT not working)