Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
204 changes: 31 additions & 173 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,183 +1,41 @@
# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.

# Created by https://www.toptal.com/developers/gitignore/api/macos,linux,jetbrains,visualstudiocode
# Edit at https://www.toptal.com/developers/gitignore?templates=macos,linux,jetbrains,visualstudiocode
# dependencies
/node_modules
/.pnp
.pnp.*
.yarn/*
!.yarn/patches
!.yarn/plugins
!.yarn/releases
!.yarn/versions

### JetBrains ###
# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio, WebStorm and Rider
# Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
# testing
/coverage

node_modules/
# next.js
/.next/
/out/

# User-specific stuff
.idea/
.idea/**/workspace.xml
.idea/**/tasks.xml
.idea/**/usage.statistics.xml
.idea/**/dictionaries
.idea/**/shelf
# production
/build

# AWS User-specific
.idea/**/aws.xml

# Generated files
.idea/**/contentModel.xml

# Sensitive or high-churn files
.idea/**/dataSources/
.idea/**/dataSources.ids
.idea/**/dataSources.local.xml
.idea/**/sqlDataSources.xml
.idea/**/dynamic.xml
.idea/**/uiDesigner.xml
.idea/**/dbnavigator.xml

# Gradle
.idea/**/gradle.xml
.idea/**/libraries

# Gradle and Maven with auto-import
# When using Gradle or Maven with auto-import, you should exclude module files,
# since they will be recreated, and may cause churn. Uncomment if using
# auto-import.
# .idea/artifacts
# .idea/compiler.xml
# .idea/jarRepositories.xml
# .idea/modules.xml
# .idea/*.iml
# .idea/modules
# *.iml
# *.ipr

# CMake
cmake-build-*/

# Mongo Explorer plugin
.idea/**/mongoSettings.xml

# File-based project format
*.iws

# IntelliJ
out/

# mpeltonen/sbt-idea plugin
.idea_modules/

# JIRA plugin
atlassian-ide-plugin.xml

# Cursive Clojure plugin
.idea/replstate.xml

# SonarLint plugin
.idea/sonarlint/

# Crashlytics plugin (for Android Studio and IntelliJ)
com_crashlytics_export_strings.xml
crashlytics.properties
crashlytics-build.properties
fabric.properties

# Editor-based Rest Client
.idea/httpRequests

# Android studio 3.1+ serialized cache file
.idea/caches/build_file_checksums.ser

### JetBrains Patch ###
# Comment Reason: https://github.com/joeblau/gitignore.io/issues/186#issuecomment-215987721

# *.iml
# modules.xml
# .idea/misc.xml
# *.ipr

# Sonarlint plugin
# https://plugins.jetbrains.com/plugin/7973-sonarlint
.idea/**/sonarlint/

# SonarQube Plugin
# https://plugins.jetbrains.com/plugin/7238-sonarqube-community-plugin
.idea/**/sonarIssues.xml

# Markdown Navigator plugin
# https://plugins.jetbrains.com/plugin/7896-markdown-navigator-enhanced
.idea/**/markdown-navigator.xml
.idea/**/markdown-navigator-enh.xml
.idea/**/markdown-navigator/

# Cache file creation bug
# See https://youtrack.jetbrains.com/issue/JBR-2257
.idea/$CACHE_FILE$

# CodeStream plugin
# https://plugins.jetbrains.com/plugin/12206-codestream
.idea/codestream.xml

### Linux ###
*~

# temporary files which can be created if a process still has a handle open of a deleted file
.fuse_hidden*

# KDE directory preferences
.directory

# Linux trash folder which might appear on any partition or disk
.Trash-*

# .nfs files are created when an open file is removed but is still being accessed
.nfs*

### macOS ###
# General
# misc
.DS_Store
.AppleDouble
.LSOverride

# Icon must end with two \r
Icon


# Thumbnails
._*

# Files that might appear in the root of a volume
.DocumentRevisions-V100
.fseventsd
.Spotlight-V100
.TemporaryItems
.Trashes
.VolumeIcon.icns
.com.apple.timemachine.donotpresent

# Directories potentially created on remote AFP share
.AppleDB
.AppleDesktop
Network Trash Folder
Temporary Items
.apdisk

### VisualStudioCode ###
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json
!.vscode/*.code-snippets

# Local History for Visual Studio Code
.history/

# Built Visual Studio Code Extensions
*.vsix
*.pem

### VisualStudioCode Patch ###
# Ignore all local history of files
.history
.ionide
# debug
npm-debug.log*
yarn-debug.log*
yarn-error.log*
.pnpm-debug.log*

# Support for Project snippet scope
# env files (can opt-in for committing if needed)
.env*

# End of https://www.toptal.com/developers/gitignore/api/macos,linux,jetbrains,visualstudiocode
# vercel
.vercel

# typescript
*.tsbuildinfo
next-env.d.ts
5 changes: 0 additions & 5 deletions .htaccess

This file was deleted.

108 changes: 75 additions & 33 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,52 +1,94 @@

[![contributions welcome](https://img.shields.io/badge/contributions-welcome-brightgreen?logo=github)](CODE_OF_CONDUCT.md)
[![Slack](.github/slack.svg)](https://join.slack.com/t/keploy/shared_invite/zt-12rfbvc01-o54cOG0X1G6eVJTuI_orSA)
[![License](.github/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)

# Keploy
[Keploy](https://keploy.io) is a no-code testing platform that generates tests from API calls.

# Keploy DevRel Program

This page has all the information you'll need for contributing to Keploy as well as kickstarting your journey as DevRel.
## Community support
We'd love to collaborate with you to make Keploy great. To get started:
* [Slack](https://join.slack.com/t/keploy/shared_invite/zt-12rfbvc01-o54cOG0X1G6eVJTuI_orSA) - Discussions with the community and the team.
* [GitHub](https://github.com/keploy/keploy/issues) - For bug reports and feature requests.

**Introduction**
# How to Contribute ??

Once you join the program, you will learn all about Keploy’s community, understand the product and showcase your contributions. You will have a chance to be involved in community, meet other contributors and establish a great network for yourself. The Keploy team is looking for ambitious individuals who wish to grow alongside, expanding their network and supporting the cause as it grows.
To Contribute to Keploy DevRel Website, please follow the following steps.

As you help Keploy achieve its mission for the future, you will also receive great benefits:
1. Fork this Repository(by clicking Fork Icon on top right of the repository).

- *Learning new skills.*
- *Personal brand development.*
- *Establishing voice for yourself and taking ownership.*
- *Building Relations with Developers.*
- *Engagement with broader developer communities and their culture.*
- *Learning about APIs and e2e testing.*

### Application Process
2. Clone this repository to your Local Machine using:
``` bash
git clone https://github.com/keploy/devrel-program

1. Apply [here](https://forms.gle/BmnmzSfuVydG7CoWA) to be a part of ***Keploy’s DevRel Program 👉*** [https://bit.ly/KeployDevRel](https://forms.gle/BmnmzSfuVydG7CoWA)
2. Once your application is submitted, you can hear from us within a week or two regarding the status of the application.
3. If your application is shortlisted, you will be invited for contribution period, which generally last a month.
```
3. Install pnpm package manager globally:
```
npm install -g pnpm
```
4. Install all the packages:
```
pnpm install

❓ **FAQ’s**
```
5. Once the required packages are installed, run the following command to build the HTML, CSS, Javascript files:
```
pnpm run build
```

- **Q: When and where can I share my thoughts about the Program?**

**A:** You are free to share your thoughts about the program whenever you want to. Feel free to send us a private message on Slack or on Discord.

- **Q: How long are the Cohort’s in the Program?**

**A:** The Program is usually a Month long, with weekly learning and tasks made to enhance your skills as a DevRel.

- **Q: I have no more free time, I want to leave the Program, what should I do?**

**A:** We understand and respect your decision, if you are willing to leave the devrel program, please connect with your Program Buddy and they will start the offboarding process.

6. Run this following command to start the application on localhost:
```
pnpm run start
```

**Contact Us** ➖ Our [Slack](https://join.slack.com/t/keploy/shared_invite/zt-12rfbvc01-o54cOG0X1G6eVJTuI_orSA)
(Alternatively you can use ``pnpm run dev`` to skip step 5, 6 and start a local dev environment.)

## Community support
We'd love to collaborate with you to make Keploy great. To get started:
* [Slack](https://join.slack.com/t/keploy/shared_invite/zt-12rfbvc01-o54cOG0X1G6eVJTuI_orSA) - Discussions with the community and the team.
* [GitHub](https://github.com/keploy/keploy/issues) - For bug reports and feature requests.
7. Make your desired changes.

8. Add, commit & push the changes, using:

``` bash
git add .
git commit -m "changes you made in the project" #Please make sure to mention which issue is closed by these changes. You can also use "cz c"
git push
```

6. Before raising a PR, please sure to 'Fetch Upstream' to avoid conflicts with existing codebase.
This is a [Next.js](https://nextjs.org) project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).

## Getting Started

First, run the development server:

```bash
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
```

Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.

You can start editing the page by modifying `app/page.tsx`. The page auto-updates as you edit the file.

This project uses [`next/font`](https://nextjs.org/docs/app/building-your-application/optimizing/fonts) to automatically optimize and load [Geist](https://vercel.com/font), a new font family for Vercel.

## Learn More

To learn more about Next.js, take a look at the following resources:

- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.

You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js) - your feedback and contributions are welcome!

## Deploy on Vercel

The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.

Check out our [Next.js deployment documentation](https://nextjs.org/docs/app/building-your-application/deploying) for more details.
Loading