If you are required to run the project in a Development environment or build your project in Debug mode, copy your local ABP token file to the following directory in your Docker container.
for Windows:
%UserProfile%\.abp\cli\access-token.bin
for Linux:
/home/user/.abp/cli/
@Shloklabs, as I see you also contacted via e-mail. I'm closing this ticket as we can continue on the e-mail channel.
Let's say you have an e-commerce website. And you have customers (tenants) in this CRM like Nike and Adidas. You want that the customer Nike will have max 100 users and Adidas will have 200 users, right? this is where the new user is being created => https://github.com/abpframework/abp/blob/dev/modules/identity/src/Volo.Abp.Identity.Application/Volo/Abp/Identity/IdentityUserAppService.cs#L77
I'm closing the issue as I see it's solved now.
Normally it's not suggested to run your production app in Debug mode as it'll run slower.
But even if you want to run in Debug mode, you need to add the AbpLicense.bin file, which you get from your development computer or log in to ABP at the production server via ABP CLI.
Note that when you log in with your account on a different computer, it'll be counted as your new development computer.
you can also check this question
Set ASPNETCORE_ENVIRONMENT to Release.
Hi,
There are 2 ABP secret keys that are custom to your organization:
ApiKey: The private key to access nuget.abp.io server. All organizations have a dedicated private ApiKey. This key is stored in the NuGet.config file. If your ApiKey is exposed, you can send an email to info@abp.io, and we can change your ApiKey. When we change it, the old key is invalidated and projects that still use that old ApiKey will stop restoring ABP packages. If your system is on production, it will still run without any problem because you are not restoring packages. But it's advised to manually update your ApiKey for your CI/CD pipeline.
AbpLicenseCode: The license code is used to validate how many and which developers are working on the ABP solution. Each developer must sign in via ABP CLI or ABP Studio to be able to write code on their ABP project. This code is stored in several appsettings.secrets.json files in your startup projects. If your AbpLicenseCode is exposed, you can send an email to info@abp.io, and we can reset your AbpLicenseCode. When we change it, the old license code is invalidated, and developers will see errors when they run their ABP project. As we use caching, the errors will arise after some time. You must manually update the old AbpLicenseCode. To get your new AbpLicenseCode, you must create a new dummy project with the same project name and copy the new AbpLicenseCode from this new project into your existing project.
ohh sorry, in your first message I just saw you tried the free version. @Engincan, why can we not get the source code of LeptonX PRO with that command?
Use this CLI command:
abp get-source Volo.Abp.LeptonXTheme.Pro
you have 2 organizations. the first one is "AKA" and it's expired. probably that's why you cannot get the new source-code. login again via ABP CLI
