Currently, fm only runs one site instance at time, provide support for running multiple fm site instance at once.
Use Case
Here are some of the use cases:
Parallel Testing: Developers can test different site versions or features simultaneously, speeding up the testing process and ensuring compatibility across various configurations.
Isolated Development Environments: Facilitates the creation of separate development environments for different branches or features, allowing developers to work independently without interference.
API Interaction Testing: Enables developers to simulate interactions between multiple instances of the site, crucial for testing API integrations and ensuring seamless communication.
Performance Comparison: Allows for side-by-side performance comparisons between different site configurations or optimizations, aiding in fine-tuning and identifying bottlenecks.
Expected Behavior
When a user creates three sites, such as one.localhost, two.localhost, and three.localhost, the expected behavior is to allow the user to concurrently open and work on all three sites in separate tabs
Current Behavior (if applicable)
When a user creates three sites, such as one.localhost, two.localhost, and three.localhost, the current behavior is that only once can be accessed at once.
Description
Currently,
fm
only runs one site instance at time, provide support for running multiple fm site instance at once.Use Case
Here are some of the use cases:
Expected Behavior
When a user creates three sites, such as
one.localhost
,two.localhost
, andthree.localhost
, the expected behavior is to allow the user to concurrently open and work on all three sites in separate tabsCurrent Behavior (if applicable)
When a user creates three sites, such as
one.localhost
,two.localhost
, andthree.localhost
, the current behavior is that only once can be accessed at once.