I'm working on a Python package where we decided to update the package's name after an initial release of the package and documentation under the old name.
Logging into the associated ReadTheDocs (RTD) account, I'm able to navigate to the projectand change the name from oldproject to newproject. That changed the display name in the "Project Dashboard" in the RTD account but doesn't affect the associated URL for the RTD build.
The project's RTD URL was initially oldproject.readthedocs.io/en/latest/index.html. I'm hoping we can update it to be newproject.readthedocs.io/en/latest/index.html. Can anyone point me in the right direction to update the URL, but retain our prior documentation build history?
It's recommended that you create a new project. You can delete the old project or perhaps create a text explaining that it's been renamed.
See: https://docs.readthedocs.io/en/stable/faq.html#how-do-i-change-my-project-slug-the-url-your-docs-are-served-at
Related
I have a website fetching the facebook events of one of my webpage thanks to a ruby script.
The script is executed within a github action before the build.
Unfortunately, the facebook token has a limited validity. I managed to find a way to renew it but I'm wondering if it is possible to update my FACEBOOK_TOKEN repository secret from a Github action ?
Of course I'm open to alternative like finding a way to have a permanent token!
Related to this 2-year-old question: BIM 360 Project creation template
Is there still not a way to replicate the Web UI option "Activate Document Management" -> "Apply a project template" that duplicates folder structure and role-based permissions?
Specifically, I'm looking at requests to create a project
POST projects https://forge.autodesk.com/en/docs/bim360/v1/reference/http/projects-POST/ supplying a template_project_id value
and then activate with
POST users/import v2 https://forge.autodesk.com/en/docs/bim360/v1/reference/http/projects-project_id-users-import-POST/
I don't see any other template input in the API documentation besides the first request, and that does not appear to bring folder structure along.
unfortunately, what you found is correct currently, creating a project from a template with folder structure and role permission is not supported with current API, but you can achieve that by yourself as shown in a sample project at https://github.com/Autodesk-Forge/forge-bim360.project.setup.tool.
This is actually a high requested wish HQ-5023 as you can see at https://fieldofviewblog.wordpress.com/2019/06/15/bim-360-acc-api-known-issues-and-wishes/#more-4424 , our engineering is actively working on that, we will update you at our blog if any progress.
Based on reading the documentation, and running some tests, this appears to be unavailable still. I would very much like to be proven incorrect by someone at Autodesk! Thanks.
I am not sure if this changed recently with the new IDE, but I thought that the deployment ID / URL of one's web app didn't change when one created additional versions. However, at this moment I am confused.
In my process.env, I have a link to my GAS URL which performs a doGet(e). However, when I go to manage deployments in my GAS file, I cannot find the corresponding deployment ID / link anywhere (not under Active nor Archived), yet, the code is working and reflects the latest changes in my script, so I believe it's the head deployment. Is this correct, or am I using some legacy deployment ID or something that's hidden?
Or perhaps asked differently, if I have the /macros/s/{deployment_id}/exec URL, is there a way within my Google account to find the corresponding script file and version / deployment?
Lastly, if the documentation recommends using versioned deployments, does this mean we have to update the GAS URL each time (e.g., if it's a public facing web app)?
Edit: others have encountered this: https://groups.google.com/g/google-apps-script-community/c/qhiqjGabQpI/m/q5i31yydCAAJ
To view the all deployment IDs, including HEAD (aka version 0):
Switch to Legacy Editor
Go to Publish => Deploy From Manifest
You'll get a list of deployment, with ID next to each one
Copy the ID of Version 0
Paste the ID in the corresponding Google Cloud Console => Configuration
Switch again to New Editor :)
If you are using Clasp with Apps Script for the development simply you can use clasp commands agents the given App Script Project.
clasp deployments to see the list of deployments including HEAD
this document maybe can help you.
Follow step 5 and step 6 in the IMPORTANT POINT.
5. Update the deployment as follows:
a. Open "New deployment" dialog with "Deploy" -> "Manage deployments".
b. For the 1st deployment, click the pencil icon for editing the deployment.
c. Set "version" as "New version".
d. When you want to change the description, please modify it.
e.Click "Deploy" button.
6.Testing
Please use above sample curl command. By this, you can confirm that sample2 is returned without changing the endpoint.
Answer:
There ways of viewing and editing deployments is set out in this article, which I will go through below. If you can not view the desired deployment using these methods, then I would urge you to contact Google Workspace support.
More Information:
As per the documentation on creating and managing deployments:
There are two types of deployments:
Head deployments, which are always synced to the current project code.
Versioned deployments, which are connected to a specific project version.
View versioned deployments
New editor:
To view the deployments of an Apps Script project, at the top, click Deploy > Manage deployments.
Find a deployment ID
New editor:
Open the Apps Script project.
At the top right, click Deploy > Manage deployments.
The deployment ID appears on the current deployment.
References:
Create and manage deployments | Apps Script | Google Developers
I am working on a production web site on a Google Compute instance.
I want to set up a staging site, and read that the quickest way to do that is to clone the production instance.
When attempting to clone it, I get the error:
Required 'compute.images.get' permission for 'projects/wordpress-sites-170807/global/images/SANITISED-template'
I've not been able to find any useful reference to Required 'compute.images.get' permission in any Google search.
Questions:
1. I only have Editor level permissions on this particular Cloud Platform console. Is this error specific to me as a user? (I am now an "Owner" of the project, so we've eliminated the likelihood of my personal permissions being an issue)
2. If this permissions issue is related to the instance itself, how do I go about changing the permissions so that it has the "compute.image.get" permission?
As discussed in this thread, using the clone button "Create Similar" button copies the configuration to a new template. It does not make a new identical instance with the exact content of your persistent disk. In your case, the configuration included the source image from a different project. Thus, Compute Engine tried to access that project and since you have no access, it threw the error.
If the goal is to clone the instance including the persistent disk you need to create a new snapshot or image from the persistent disk, and then to retain other configs, you may use the clone button, but change the source image to the snapshot or image you have created earlier.
If the goal is creating a new instance from that original image in the other project, you need IAM roles in that project. For further information about the subject check this document
UPDATE:
The Google Cloud Console interface was updated several weeks ago, and the "CLONE" button was replaced by "CREATE SIMILAR".
I am attempting to publish a simple Google Docs add-on, following these instructions: Publishing an Add-on
However when completing the configuration for Google Apps Marketplace SDK, I enter my script project key (found from file --> project properties) and receive the following error: 'Project Key is not associated with the current project.'
Only instance where I can find someone with the same problem (here) occurred when they created a project on the Google Developers Console instead of going through resources --> Advanced Google Services. This is not the reason for my error, can anyone shred any light onto my problem?
Any help would be gratefully received,
Connor
Kept trying, did not change the way I tried publishing nor the project key I was entering and it worked after so many retries. Wish I could give a more detailed answer...
I was able to fix by combining two successful responses from this post:
use version number, and only the number, e.g. "1" -- Do not use "v1.0" or "Version 1 on Oct 1, 6:10 AM" or your deployment's Description
After completing step 1, delete your entry in field 'Docs Add-On Project Script ID', then re-enter it -- the page seems to not re-evaluate your changes unless you do this; I had tried saving multiple times before doing this with no success using the correct version number and script ID.
For me I need to go Publish->Deploy as API. Select the correct version and then the publish screen worked
I needed to include a correct version number (1,2,3,4; not "v0.1") in addition to the script ID. The error suggested my script ID was wrong, but the error went away when I picked a valid version number.
For me, the Google App Script file needed to be associated with the project.
In the GAS, go to Resources > Cloud Platform Project.
Under Change Project, enter the project number (which can be found on the home page of the Google Cloud Platform Project in the Project info module), and click Set Project.
Confirm the notices (though make sure that is really what you want to do).
Once it has been set, go back to the App Configuration, and re-enter the information (if you are already on that page, refresh).
That's what worked for me, but maybe other developers get that error for other reasons.
Source: https://developers.google.com/apps-script/guides/cloud-platform-projects#switching_to_a_different_standard_gcp_project
Hmm I had issues as well. It didn't work with version 1 in "Docs Add-on script version" but while I tried a bunch of stuff I ended up deploying again and then I incremented version to "2" and then it worked.
I got the same error today, I made it finally work. I will go through the fields I checked.
App Integration [I'm deploying using deployment ID, you can get the ID from AppScript manage deployment]
Choose which workspace you are releasing [In my case Sheets], type the version from AppScript.
Enter all other general Credentials and save.
The above steps worked for me.
Try to use the Google Workspace Add On and enter the App Script Deployment ID. That accepted for me and showed it as a Sheets Add-On
It's different in deploy or test in legacy editor and new editor.
And I'm using legacy editor before
(because some following steps from documents is not work in new editor),
So when I lookup Mange deployment in new editor,
It wasn't exisisted,
And the deployment ID it's not work when I fill out App configuration in Google Workspace Market.
For me I just change to following the Legacy editor's following steps
https://developers.google.com/workspace/marketplace/enable-configure-sdk#legacy-editor_2
and It works.
Looks like it is not possible to change scriptId after a round of review. So you can just update only version. I changed to last number of deployment version like '6' and it is saved.